Schedules

Use recurring schedules for predictable project work with a clear prompt and bounded scope.

Before you begin

Run the intended task manually once. Define the cadence, timezone expectation, project, owner, and what should happen when a previous run is still active.

Create a Graph planning and failure UserGroup before opening the form. All current members of this UserGroup receive failed-run alerts. At least one current member must have project operator access to the exact project; graph-planning questions go only to members with that access. Create schedule remains unavailable until Name, Prompt, Graph planning and failure UserGroup, and a valid five-field cron expression are present.

At every occurrence, Labor0 submits the exact complete Prompt for reviewable planning. Review and approve the resulting plan before execution can begin. Include the scope, expected output, and success criteria. Do not include secrets, credentials, tokens, personal information, or customer data.

Example schedule

This example schedules a weekly documentation review report for planning and review.

Field	Example input
Name	`Weekly documentation gaps`
Prompt	`Review public documentation changes from the last seven days. Report broken links and missing examples.`
Graph planning and failure UserGroup	`Documentation owners`
Preset	`Monday at 09:00`
Five-field cron expression	`0 9 * * 1`
Timezone	`Asia/Seoul`
Optional runtime settings	Leave Project default for the first run

Procedure

Open the target project and select Schedules from its top-level navigation.
Enter Name, the bounded Prompt, and Graph planning and failure UserGroup.
Choose a Preset or enter a Five-field cron expression, then confirm Timezone.
Select Preview next five. Check both the UTC and local times before saving.
Leave Optional runtime settings at Project default unless the manual test proved a specific Runtime, Model, Reasoning effort, Runner selection, Plan mode, Fast mode, or Graph-change auto-approval value is required.
Select Create schedule and open its detail page.
Confirm the schedule is ACTIVE, its Next time matches the preview, and its first result appears under Run history.

Expected result

The Schedules list shows Weekly documentation gaps, 0 9 * * 1 · Asia/Seoul, a future Next time, and Latest: No runs until the first occurrence. After an occurrence, Latest shows the planning submission state and the detail page records both Revision history and Run history. Approve the resulting plan before the report can be produced. Pausing changes the schedule state to PAUSED without deleting its history.

Unattended Graph changes

Schedules have a three-state Graph-change auto-approval setting: Project default, Enabled, or Disabled. Existing schedules use Project default, and the Project default itself is disabled until a project operator opts in. The effective value is captured when each scheduled prompt is accepted, so editing the schedule or Project setting affects only later runs.

Enabled runs can commit validated Graph changes without a reviewer online. A temporary failure is retried automatically; if automatic approval cannot finish, Labor0 keeps the preview pending, notifies the normal review audience, and restores Approve, Request changes, and Discard. Open the review warning and recover through those ordinary actions rather than creating a duplicate schedule or run.

Permission guidance

Creating or changing schedules is a project administration action. Keep schedule ownership with someone who can pause it when the outcome changes.

If a run is late

Symptom: a scheduled task has not appeared. Likely cause: the schedule is PAUSED, the timezone or next occurrence differs from expectation, billable execution is unavailable, or a project prerequisite is blocked. Safe recovery: compare Next with the five-occurrence preview, correct the named issue, and wait for the next eligible occurrence. Do not create a duplicate schedule as a retry.