From 8a9e199badcf99a54045edb0efc35608d5dba4ae Mon Sep 17 00:00:00 2001 From: iris Date: Sun, 4 Oct 2026 17:25:26 +0200 Subject: [PATCH] docs: schedules page section passes the prose lint --- docs/swarm/ui.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/swarm/ui.md b/docs/swarm/ui.md index b88de031..1e462ddb 100644 --- a/docs/swarm/ui.md +++ b/docs/swarm/ui.md @@ -42,15 +42,16 @@ when it fires next. **edit** turns the card into its own form; **pause** and **+ schedule** opens an empty form above the list, and the filters narrow the list by name, agent or state (`active`, `paused`, or `past` for a one-shot whose time has passed). `past` is the controller's clock against the start time, -not a record that an agent fired, so a `past` schedule can still be paused. +not a record that an agent fired, so you can still pause a `past` schedule. A schedule repeats **every** some number of seconds, minutes, hours or days, or fires **once**. Its start time is the moment a one-shot fires, and the origin of the fire times of a repeating one. The form previews the next three fire times. +Changing the start or the repeat moves them; editing only the name, message or +agents doesn't, and the form warns when an edit would. + A start in the past fires the latest missed time once, right away, in every agent chosen, and the form says so. -Changing the start or the repeat moves them; editing only the name, message or -agents does not, and the form warns when an edit would. Only an operator can change a schedule here or with `swarmctl schedule`; an agent has no way to add one. The page needs the controller's `/api/schedules`