Schedules
Background jobs on any schedule
Run tasks at any interval. Every minute, daily at 9am, weekly on Mondays. Durable execution means your jobs survive worker restarts and keep running reliably.
Capabilities
Cron Expressions
Standard cron syntax for flexible scheduling. Every minute, hourly, daily, weekly, monthly. Whatever you need.
Durable Execution
Jobs survive restarts and infrastructure changes. Never miss a scheduled run.
Status Tracking
See last run time, next run time, and execution logs. Know exactly what's happening.
Manual Triggers
Run any scheduled job on demand. Test it, trigger it early, or re-run after a fix.
Pause & Resume
Temporarily disable schedules without deleting them. Maintenance mode made easy.
Execution History
Full log of past runs with timing, status, and output. Debug issues quickly.
Use Cases
Why It Matters
- Set and forget. Schedules run reliably without babysitting.
- Durable execution ensures jobs never get lost
- No separate cron service to manage
- Full visibility into execution history
How It Works
Schedules in Runwork let you run tasks at any interval—every minute, hourly, daily at 9am, weekly on Mondays, or any custom cron expression. Unlike automations that respond to events, schedules run on a timer, perfect for recurring background work that needs to happen reliably.
Creating a schedule is straightforward. Define when it should run using standard cron syntax, then specify what it should do. Schedules can query your entities, call integrations, trigger workflows, or run any custom logic. The Work Assistant can generate schedules from descriptions like "send a weekly summary email every Monday at 9am."
Durable execution is the key differentiator. If infrastructure restarts or workers recycle, your schedules keep running. Missed runs are detected and handled according to your configuration—catch up immediately, skip to the next interval, or alert you. You never lose a scheduled job.
Every schedule tracks its execution history. See when it last ran, when it will run next, how long each execution took, and whether it succeeded or failed. Debug issues quickly with full logs of what happened during each run. Manual triggers let you test schedules or run them early without waiting for the next interval.