Jobs & Scheduling
The async engine underneath the platform: a durable job queue that retries, a real cron scheduler, and one record of every run — scheduled or event-driven.
Durable jobs
Background work runs on a durable queue — NATS JetStream or Redis, your choice. If a job fails, it retries on its own with a growing delay, and anything that stalls gets picked back up. And a job only starts once the change that created it is committed, so nothing fires on work that rolled back.
Scheduler
Scheduled jobs run on standard cron, validated before they're saved. Enable or disable one, run it now, and see when it last ran and runs next. Missed runs can catch up to a limit you set, and you decide whether a job may overlap itself.
Run history
Whether a job ran on a schedule or fired in reaction to an event, it lands in one history — what ran, when it started and finished, and how it ended. Filter by status or by source, and cancel a job that's still pending or running.
Keep exploring