Run work on a schedule
Section: DOC-CP-scheduling#run-work-on-a-schedule.
Send a weekday digest, deliver a reminder at a chosen time, or refresh application data at a regular interval. Create a job that calls your endpoint on that schedule, then follow its delivery history and recover failed attempts.
Start here
Section: DOC-CP-scheduling#start-here.
| Build this feature | Recipe |
|---|---|
| Generate a weekday briefing for a user | Automate recurring agent work |
| Call your application at a chosen time | Create a reminder or calendar job |
| Let a user reschedule, pause or remove a reminder | Manage the reminder lifecycle |
| Recover a reminder that failed to reach your app | Trace execution and retries |
| Implement the callback receiver used by these recipes | Accept authenticated callbacks safely |
How it works
Section: DOC-CP-scheduling#how-it-works.
For a daily briefing, the scheduler calls your backend at the selected time; your backend accepts the firing, performs the work and records its business result.
- Build a callback receiver that verifies the signed request and saves accepted work durably.
- Create the job with that receiver, the intended user and a calendar/timezone or one-time timestamp.
- Save the returned schedule identifier and show the next trigger time in your application.
- Follow the first firing through execution history and your receiver’s business outcome.
- Give the user a way to change or stop future firings, while accounting separately for work already accepted.
A successful scheduler execution means your receiver acknowledged delivery. It does not prove the briefing was generated or shown to the user. The agent briefing recipe connects those later steps.
Choose when the work should run
Section: DOC-CP-scheduling#schedule-types.
| Your application needs | Recipe variant |
|---|---|
| A weekday digest at the user’s local time | Use a calendar schedule |
| One reminder at a chosen instant | Use a one-time schedule |
| A refresh at regular elapsed intervals | Use an interval schedule |
The timing reference defines timezone handling and field defaults.
Related
Section: DOC-CP-scheduling#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
Document ID: DOC-CP-scheduling. Section identities and revisions.