Schedule a governed loop deliberately

Enable a schedule only after reviewing the current executable steps, first-run time, time zone and recurrence. A saved draft, an agent suggestion or a cadence written in prose does not enable future work. Scheduled runs still use the workspace's permissions, approvals and spending limit.

Before enabling

Open the intended loop in Loop Builder. Check every step's configured function and arguments. Preserve the current draft, confirm authorization for future execution and review Permissions & spending. Do not use a schedule as a way to bypass approval or run limits.

This schedule uses governed function workflows, not a hosted artifact version. Follow hosted version review separately when that is the object you have.

Choose when it should run

1. Open More loop actions, then Schedule.
2. Set First run to the intended local date and time.
3. Check Time zone. Use the intended IANA time-zone name rather than assuming the browser's current zone is correct for the task.
4. Set Repeat to Once or Every interval. For an interval, enter the intended number of minutes.
5. Review the current canvas again, then choose Enable schedule.
6. Confirm the enabled record, next-run observation and recurrence. Keep the schedule identity and its workflow relationship.

Daylight-saving boundaries

Repeats use elapsed minutes, including across daylight-saving changes; an interval is not a guarantee of the same local wall-clock time every day. If the initial local time is rejected as ambiguous or nonexistent, select an unambiguous time in the intended zone. Do not change zones merely to silence a validation error.

Enabling first prepares a workflow without starting it immediately, then submits the schedule. If the canvas changes while preparation is pending, review the current functions and enable deliberately again. Do not assume an existing schedule automatically adopts later canvas edits.

Follow scheduled work

Open the schedule's Run history and inspect the actual run. No history means no recorded scheduled run, not a successful background task. Waiting work pauses the next run. Use run review to distinguish waiting approval, completion and acceptable output.

Pause or resume

Choose Pause schedule on the intended enabled record, then confirm it reports paused and no next run. This stops future scheduling; it does not recall dispatched actions. To resume, inspect the same schedule and current authority before choosing Enable schedule. Review existing runs separately.

An enable response was lost

Inspect the schedule list and its workflow before submitting again. Keep the original request identity and unchanged inputs while the outcome is unconfirmed. A failed response does not prove that no schedule was stored. Retain the exact error and ask for help rather than creating another schedule with a new identity.