Schedules & runs

The schedules panel is the cabinet’s read-only view of every scheduled task in the workspace and the history of every run. Authoring new schedules has moved out of the cabinet; the surface is intentionally lean.

What is in the cabinet

For each schedule you see:

• Name and description.
• Next run time (human and ISO).
• Last run status — success / failure / cancelled / running.
• Owner — the member who authored it.
• Target machines — single machine, group by tag, or fan-out.

Run history covers the last N runs (per plan retention).

Inspecting a run

Each run drills into:

• Start and end timestamps.
• Exit code and duration.
• Captured stdout and stderr.
• Triggering user (or system for cron).
• Associated session ID — link to Sessions inspector.

Cancelling a schedule

Owners and Admins can:

• Pause — stops new runs without deleting; resumable.
• Cancel running — sends SIGTERM to the in-flight run; SIGKILL after grace.
• Manual rerun — Admin-only; runs the schedule once, out of cycle.

Pausing keeps the schedule’s history intact. Deletion is not exposed in the cabinet; remove via ../../cli/trigger or by editing the source skill.

What is not here anymore

The “Create schedule” button is deprecated. Author new schedules via:

• Skills — declare schedules in skill.md. Best for reusable automations.
• CLI — cmdop trigger create for ad-hoc one-offs and cmdop session schedule for persistent multi-command runs.
• Desktop — schedule editor in Settings (when shipped; track desktop release notes).

Failure handling

If a run is stuck (no heartbeat for 2× expected duration):

• Marked degraded; alert fires per Usage & quotas integrations.
• Next scheduled run still fires unless overlap protection is enabled.
• Manual rerun available for Admin to retry without waiting.

Where this data lives

Backed by the Django schedules app (schedules, runs, run commands); rendered by apps/my/.../dashboard/schedules/.

Related

• Sessions inspector
• Audit log
• Skills: skill.md
• cmdop trigger