Automation schedules and runs

An automation can be manual-only, run once at an absolute time, or recur on a fixed-period schedule. d5s avoids duplicate and overlapping runs.

Scheduled runs

Hourly schedules run at the same minute every hour. Daily and weekly schedules follow the configured timezone so the selected local time stays stable across daylight-saving changes.

After an interruption, d5s attempts one due recurring run and then resumes the schedule. It does not replay every missed interval.

A one-time schedule has no later slot. It turns off after its run starts. If the run cannot start yet, d5s tries again later without creating a duplicate.

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 under the same rules as 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 one-run-at-a-time rule as scheduled runs. It does not rewrite the recurring schedule.

Manual and scheduled runs follow the automation creator's no-training preference and any organization requirement.

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 work that is not due yet, a paused automation, a skipped occurrence, and a run that started but failed.

A full subscription pace window does not block an occurrence when purchased credits are available. If the organization balance, a full pace window without purchased credits, 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. With a limit of 2 or more, the agent uses the last step to write its answer, not to run tools. So a limit of 5 leaves 4 steps for tool work.