Skip to main content

​
Outcome

The schedule is enabled only after one manual run produced the session and the output you expected, and next_run_at shows the tick you intended in UTC.

​
Before you start

  • The roster agent exists with a default template, or you have a template id and a coding agent to run as.
  • The prompt the schedule sends is written down. It is sent verbatim on every tick.
  • If the run should post somewhere, the Slack integration and channel id are known. Email and WhatsApp targets are set in the dashboard.

​
Do it

1

Create it disabled

On Agents, open the Scheduled tab and click New scheduled agent. Fill in Name this scheduled agent and the prompt (“Describe what the agent should do on each run…”). Choose Agent to run as a roster agent, or Harness to pick the coding agent and template yourself. Set the schedule, pick Personal or Team, and leave it off.
2

Run it once

Use the row’s menu and choose Run now. This executes the identical code path a cron tick takes: same template resolution, same post target, same launch. A failure here is the failure you would otherwise get at the scheduled hour.
3

Read the session

The run appears under Sessions. Open it and read the transcript to the end: did it reach the tools, did it finish, did the post land where you meant? If the schedule runs as a roster agent, check the run’s grade too.
4

Enable

Toggle the schedule on. Then read next_run_at; it is the fastest liveness check and should be the UTC instant you intended.

​
Verify

last_run_at is set from the manual run, enabled is true, and next_run_at is in the future at the hour you expect. After the first tick, last_session_id changes and a new session appears.

​
Gotchas

  • Cron is five fields in UTC, with no per-agent time zone. “9am Pacific on weekdays” is 0 16 * * 1-5 in winter and 0 17 * * 1-5 in summer. Pick one and note the DST shift, or express the schedule in UTC to your team.
  • A 503 on create or enable means the scheduler is not configured for this deployment. Create the agent disabled and drive it with Run now until it is.
  • Enabled but never run. enabled true, last_run_at null, next_run_at in the past: the schedule was never validated. Disable, run now, read, enable.
  • One post target. A schedule posts to one Slack channel, one email address or one WhatsApp number, never several. With no target the run is visible only in the dashboard.

5. Prove it works and iterate

Seeded cases, grades and the scorecard, and why the first run is always on demand.