Schedules

Create recurring or cron-based schedules that start Agent runs in a project.

Control → Schedules manages scheduled Agent work in the current Project.

These are not Workflow schedules. If you need a recurring Workflow trigger, use Scheduling workflows under Build and improve → Automate.

Create an Agent schedule with task or heartbeat kind, recurring or one-off cadence, timezone, session behaviour and prompt.

What you can schedule

The current form supports:

• Kind — Task or Heartbeat. A Project can have at most one Heartbeat.

• Cadence — recurring cron or one-off.

• Cron expression — recurring schedules default to 0 9 * * *.

• Time zone — initialised from the browser's IANA timezone, for example Europe/Amsterdam.

• Session — start a new session or reuse a session.

• Description — an administrative note about the schedule.

• Prompt — the instruction sent to the Agent when the schedule fires.

The populated list shows each schedule's kind, cadence and timezone, status, last run and next run, with controls to edit, pause or delete it. There is currently no Run now control, so testing a schedule means waiting for its next scheduled fire.

Access and navigation

Creating, changing, pausing and deleting schedules requires Builder-level Project access. The underlying read surface is Project-member scoped, but Operators do not see the Control section in the current navigation.

Schedules is also an exception to the normal Control tab strip: it is available from the Control sidebar item but is not currently present in the horizontal Control tabs. Use the sidebar or the direct Schedules page rather than looking for a Schedules tab.

Before relying on a schedule

Check the timezone, the Project the Agent will run in, and whether the Agent has the Skills, Connections and maintained context needed to do the work without an operator driving the session.

A scheduled Agent run changes when the work starts. It does not by itself turn an ambiguous foreground task into a well-defined autonomous process.