Watch
0
0
Fork
You've already forked hyperhive
0

swarm-ui: schedules page says what a past start does, no longer claims a one-shot fired

A start in the past fires the latest missed time once, right away, so the
form says that instead of 'already passed'. A one-shot past its time reads
'past' / 'time passed' (the controller's clock, not a record of firing) and
keeps its pause button. The edit form compares against what it opened with,
so a schedule changing under it is not reverted on save.
This commit is contained in:
iris 2026-10-04 17:07:29 +02:00 • committed by mara
commit 0af7f53e88
4 changed files with 45 additions and 31 deletions

View file

@ -40,12 +40,15 @@ title, with the **agents** it fires for, the message, how often it repeats and
when it fires next. **edit** turns the card into its own form; **pause** and
**resume** stop and restart it; **remove** deletes it after a confirmation.
**+ schedule** opens an empty form above the list, and the filters narrow the
list by name, agent or state (`active`, `paused`, or `done` for a one-shot that
has fired).
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.
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.
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.