wasp-jobs

Background jobs in Wasp run asynchronously using PgBoss, a PostgreSQL-backed job queue. Define a job in your Wasp file, implement its handler function, and trigger it from actions or scheduled cron expressions. Jobs execute independently without blocking the main request cycle, keeping your app responsive.

Yes. Queue email tasks as background jobs using PgBoss. Trigger the job immediately after signup or other events, and PgBoss handles delivery in the background. This prevents UI timeouts and ensures reliable delivery even if the initial request fails.

PgBoss, the job executor for Wasp background jobs, requires PostgreSQL as its backend. All job state, queuing, retry logic, and scheduling data is stored in PostgreSQL, so you must have a PostgreSQL database configured for your Wasp application.

Define scheduled tasks in your Wasp job configuration using cron expressions. PgBoss interprets the cron syntax and triggers your job function at the specified intervals. You can also trigger jobs programmatically from actions with custom delay and retry controls.

PgBoss automatically retries failed jobs according to your configured retry policy. You can set retry counts, backoff delays, and expiration times. Failed jobs are tracked in PostgreSQL, allowing you to monitor, debug, and manually retry if needed.

Yes. Long-running operations like data processing or report generation run as background jobs outside the request cycle. PgBoss queues and executes them asynchronously, eliminating timeout constraints while keeping your application responsive to user requests.