Automation schedules and runs

An automation can be manual-only, run once at an absolute time, or recur on a fixed-period schedule. The run policy is designed to avoid duplicate and overlapping work.

Scheduled runs

Sub-day schedules use rolling intervals. Daily and weekly schedules follow the configured timezone so the selected local time stays stable across daylight-saving changes.

When the scheduler has been unavailable, missed recurring slots coalesce. d5s attempts one due run and computes the next slot strictly after the current time; it does not replay every missed interval. This prevents an outage from creating a burst of stale work.

A one-time schedule has no later slot. It disables itself only after its occurrence is accepted. Temporary failures or busy periods keep it due for retry, without creating duplicate runs.

Pausing an automation prevents scheduled work until it is resumed. Existing run results remain available. Review the displayed timezone and next due time after changing the cadence.

Agents with edit permission can change the schedule through the automation tool. The same schedule validation and next-run calculation apply to edits made by agents and people. Following an automation for result notifications does not give an agent permission to edit it.

Manual runs

Run now is useful for testing instructions or producing an out-of-cycle result. It uses the same project, model, reasoning, instructions, quota, enabled connectors, and nonoverlap policy as scheduled runs. It does not rewrite the recurring schedule.

Manual and scheduled occurrences use the automation creator's effective no-training preference, plus any organization requirement. The same frozen policy applies to auxiliary model calls and sub-agents started by that occurrence.

Concurrency

Only one run of an automation can be active at a time. If another occurrence or Run now arrives while it is active, the second request is skipped instead of starting overlapping work.

An optional daily quota counts runs over the previous 24 hours. When the quota is reached, a new run is skipped. Retries do not create duplicate runs for the same scheduled occurrence.

Use run history to distinguish four cases: the scheduler has not reached the due time, the automation is paused, the occurrence was skipped by a guardrail, or a session was created and then failed during execution.

If the organization balance, a pace window, or the automation owner's member spend limit blocks an occurrence, it does not run. A recurring schedule continues to its next occurrence; a one-time occurrence remains eligible for a later retry.

Execution limits

An optional maximum-step limit applies to both scheduled and manual runs. Set it to an integer from 1 through 100. When omitted, the standard per-run step limit applies.