Scheduled Jobs
Durable time-based jobs that call an HTTP endpoint you own — on a cron schedule, once at a fixed time, or on a repeating interval. Jobs survive restarts, retry on failure, and keep their own execution history.
Concepts
| Concept | Description |
|---|---|
| Job | A named schedule that fires an HTTP target at computed times |
| Schedule type | How fire times are computed: cron, one-shot, or recurring interval |
| Target | The HTTP endpoint and payload the job delivers to on each firing |
| State | Lifecycle of the job: SCHEDULE_STATE_ACTIVE, SCHEDULE_STATE_PAUSED, SCHEDULE_STATE_DELETED |
| Execution | A single firing record — captures status, HTTP result, attempt number, and duration |
| Auto-pause | Automatic pause after N consecutive failures — prevents runaway retries against a broken target |
| Retry policy | Exponential backoff between delivery attempts within a single firing |
Schedule Types
| Type | Field | When to use |
|---|---|---|
SCHEDULE_TYPE_CRON | cron_expression | Repeating schedule aligned to calendar time (e.g. every weekday at 9 AM) |
SCHEDULE_TYPE_ONCE | scheduled_at | Fire exactly once at a specific UTC timestamp |
SCHEDULE_TYPE_RECURRING_INTERVAL | interval_seconds | Fire every N seconds, regardless of clock alignment — minimum 60 |
Where to next
| Page | Covers |
|---|---|
| Creating Jobs | Cron, one-shot, and interval schedules |
| Managing Jobs | Get, list, update, pause, resume, delete, external ids |
| Execution & Retries | History, retry policy, auto-pause |
| Verifying Callbacks | Proving a dispatch came from the platform before acting on it |
Related
- Authentication & API Keys — Keys and acting on behalf of a user
- Webhooks — Receiving platform events rather than scheduling your own
- Scheduler API Reference — Full endpoint reference