Schedule
Schedule is under Activity → Schedule. It has two kinds of jobs plus shared Analytics and Logs.
- One-time — run a top-level agent or workflow at a datetime or after a timeout. Optional input matches the target’s input schema. Jobs are backed by the workspace job runner (Agenda). After a successful or failed run, the one-time row is removed from the list.
- Repetitive — a cron expression (UTC) that fires a handler workflow or a mapped resource, the same routing model as event handlers. Existing cron handlers from Event handlers appear here.
When to use
- Run an agent or workflow once at a set time, or after a number of minutes
- Repeat work on a clock (nightly cleanup, hourly sync) without an external scheduler
- Review run volume and individual attempts on Analytics and Logs
One-time
Open Activity → Schedule → One-time. Use the Create one-time schedule panel:
| Setting | What it does |
|---|---|
| Name | Required label |
| Trigger mode | Specific time or Timeout (minutes) |
| Scheduled at | Calendar datetime (specific time mode) |
| Timeout (minutes) | Integer ≥ 1 (timeout mode) |
| Target type | Agent or Workflow |
| Target | Eligible top-level agent or workflow (general channel, not linked) |
| Input | Values for the target’s input schema when it has one |
Choose Create schedule. From the list you can Edit schedule (target is locked) or delete.
Statuses include pending, running, success, and failed.
Repetitive
Open Activity → Schedule → Repetitive. Click Create task, set a name and cron expression, then configure mapping in Setup (free-form handler workflow or a mapped resource). Enable or disable the task like any event handler.
Cron expressions run in UTC. Event args include args.cron (the expression that fired).
Run now on the task fires that same workflow once, without waiting for the next tick and without changing the schedule. It works while the task is disabled. The repeating job still runs only while the task is enabled. The attempt shows up on Logs.
Typical uses:
- Nightly or weekly jobs: digest, report, or query
- Recurring sync without an external scheduler
- Cleanup: archive stale table rows or retry failed work on a clock
Analytics and logs
Analytics charts run volume. Logs lists individual one-time runs (schedule.run) and repetitive fires (event-handler.fire), including skipped and failed attempts. Open a log row to jump to the one-time list or that repetitive task.
Each repetitive task also has its own Analytics and Logs on the task detail.
Use schedule blocks in agents and workflows
In the builder, system schedule blocks still create one-shot jobs only:
| Block | What it does |
|---|---|
| Schedule Now | Run the target immediately via the scheduler |
| Create Schedule | Create a one-shot schedule |
| Get Schedule | Read schedule details |
| Update Schedule | Change timing |
| Delete Schedule | Remove a schedule |
Pass input with path bindings or Liquid-aware fields; use env.* for secrets as described in Variables.
Limits
- One-time targets must be general agents or workflows.
- Repetitive tasks use event-handler mapping (handler workflow or an existing resource).
- Inactive repetitive tasks do not fire.