Scheduled execution

Today every run starts because a caller asks for it: your backend, the Console, or the CLI. Scheduled execution lets the platform start runs on a cadence you declare, with the same session, policy, and evidence rules as a run you start by hand.

Under construction

This page is planned and not yet written, because the capability it describes is not yet generally available. The structure is here so you can see where it fits; the notice comes off when it ships.

What this page will cover

• Declare a schedule for a deployed version and the tenants it runs for.
• What each scheduled run starts with: prompt, workspace, and durable work.
• Overlap, missed windows, and pausing a schedule.
• How scheduled runs appear in events and evidence.

Meanwhile

• Invoke from your application shows how to start runs from your own scheduler today.
• Automation credentials covers the machine identity a scheduler would use.
• Durable work and settlement explains how a later run continues the same unit of work.