Distributed Job Scheduler · View 04 of 20 · People and journeys
What the trough says
- The sentiment line drops at the policy screen, not at the cron expression. Writing 0 9 * * 1-5 is easy; being asked what should happen to the fires missed during an outage is not.
- That is a structural finding, not a UX one: the answer has to be declared before the outage (ADR-06), so the question cannot be deferred to the moment it matters.
What answers it
- A default of fire-once-now, so the common case needs no decision and the unsafe case needs an explicit one.
- Dry-run on the production code path, so the next three instants a developer sees are the instants the scheduler will use (ADR-05).
- A published p99 lateness budget, so "three seconds late" has an answer other than a guess.
Assumptions
- A developer's first scheduled job is a calendar recurrence in a named zone, not an interval. The zone picker is therefore on the primary path rather than behind an advanced toggle.
