Scheduled tasks

A site can run background jobs on a schedule — no external cron service, no separate worker to host. You define a task and when it should run, and the platform runs it.

What they're for

• Reports and digests — email a weekly summary, roll up yesterday's submissions.
• Reminders — nudge users about an appointment, an expiring trial, an abandoned cart.
• Cleanup and maintenance — prune stale records, recompute values, sync with an external system.
• Recurring integrations — pull data from an API on an interval and store it.

How they work

You schedule a task to run at an interval (down to every 15 minutes) and it runs in the background at those times, in the site's timezone. A task has the same abilities as a handler: it can read and write the database, send email, call external APIs, and broadcast to realtime channels.

Working with larger jobs

Tasks are suited to batch work — processing many records, sending many messages — and can be written to pick up where they left off, so a large job progresses safely across runs rather than trying to do everything at once.

Where to see them

Scheduled tasks are part of a site's logic, so they travel with the project when you pull and publish. Their output and any errors show up in the site's logs.