Skip to main content
Scheduled runs start with no person present. By default each run of a schedule continues the same conversation, so the agent sees its earlier runs.

Recurring schedules

On the agent’s home, Manage schedules opens Scheduled runs, with every schedule and queued run for the agent. Add schedule has two tabs: Simple (describe it in a sentence) and Advanced (Interval, Daily or Weekly, at a time in your time zone). The Runs line shows the time in your zone and in UTC, and the cron on hover. Conversation sets where the runs go: Same conversation (the default) or New conversation each run. A workflow’s schedule has no Conversation choice; it offers a Model instead. Schedules are stored in UTC and do not follow daylight saving. A 09:00 Los Angeles schedule saved in October runs at 08:00 after the clocks change in November, so edit it after a clock change if local time matters. The shortest interval is five minutes. Every edit publishes, and a schedule fires only once it is live.
New schedule dialog, Advanced tab, with Interval, Daily and Weekly, a time picker with a time zone, a Runs line with the local and UTC time, Instructions, Run notifications, and Conversation set to Same conversation

Add schedule, Advanced tab: daily at 09:00 Los Angeles time, which the Runs line shows as 17:00 UTC in November. Shown with sample data.

Over the API, schedules live under /v1/agents/{agent_id}/scheduled-tasks (GET, POST, PATCH, DELETE). Fields are cron, prompt, title, enabled and an optional model. POST /{task_id}/run fires one now, and enabled: false pauses it. Managed schedules that xpander owns, such as a heartbeat, can be paused or run but not edited or deleted. A schedule runs as the person it was set up for. If that person leaves the organization, the schedule turns itself off, the run is skipped, and the agent’s creator gets a Schedule paused notification. When the creator is the person who left, nobody is notified. To restart it, an admin does these steps:
  1. Open Manage schedules and click the schedule.
  2. Under More options, set Runs as to a current member.
  3. Click Update. The editor saves and closes.
  4. Click the schedule again, then click Resume.
The agent’s creator can open the schedule, but Runs as stays locked to the person who left. The creator asks an admin to restart it. A key that speaks for no person (the organization’s default key or an agent key) gets 403 when it changes who a schedule runs as, or edits or removes a schedule that runs as someone.

Re-checks the agent books itself

An agent can book a one-off run to look again later. It shows in the conversation as a Next run line with a countdown, Show prompt and Cancel. You can also cancel with DELETE /v1/agents/{agent_id}/self-schedules/{schedule_id}. This is a per-agent switch, with a cap of three pending runs per task by default. A repeating re-check is a chain of one-off runs the agent renews, never a loop it cannot leave. To change one before it runs, open Manage schedules and click it under Upcoming runs. Upcoming run shows the full prompt and time, with Open conversation, Cancel run and Edit, which changes the prompt and the Run time (your local time). A run that is already due cannot be edited, and people with view access cannot edit or cancel.
Upcoming run dialog: Runs Nov 3, 2026, 1:50 PM, the prompt Re-check the alert, Open conversation, Cancel run and Edit

An upcoming run the agent booked, opened from Manage schedules. Shown with sample data.

How a scheduled run reports

Each fire is a turn with the source Scheduled in the Session manager and the Source filter, and Scheduled in the Status filter lists runs still to come. On a coding-CLI agent, if a booked run comes due while the agent is still working in that conversation, the prompt reaches the running process as its next message (“The follow-up scheduled earlier in this task is due now”). Otherwise it starts a new turn. A schedule created from a Slack channel binding replies in that channel. A failed fire is not retried: the next fire is the retry. While the agent is INACTIVE, fires are skipped and booked re-checks are marked failed. Notifications follow the agent’s settings, and a schedule can opt in to its own.

What an unattended run may use

The run acts as the agent’s background user. Budgets and approval windows apply as on any run. See Permissions.

Next steps

Set what an agent may do

Budgets, approvals and access.

Use per-person sign-in on unattended runs

Behaviour with nobody signed in.