Show when a plan's scheduled run was skipped, and why, outside the daemon's log
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The design is in §5 and §16 of docs/design/scheduling-and-config.md; read the overlap-policy and scheduler passages first. Trace the scheduler's skip path to where PlanSchedule is updated and the plan response is built, then the plan page and start-page list that would render it. Done means a skip's time and localized reason code live on PlanSchedule, appear in the API and UI, clear at the next run start, and both design sections are updated.
Written by the indexing model from the issue text.
Description
What happens
A plan's scheduled run that its overlap policy skips leaves no trace outside the daemon's log. The plan pages, the start page and the operation history all show nothing for it, so from the UI the run looks like it silently didn't happen.
Seen on 0.3.1 (macOS, hourly cron = "0 * * * *", default overlap):
- 18:46 local: a backup started by hand.
- 19:00:00: the log says
the scheduled run of plan … was skipped: its last run is still running. - 19:01: the manual backup ends
Succeeded.
Nothing in the web UI says the 19:00 run was skipped or why. The only way to find out is to read the log file.
Why it's this way today
This is the design, not a defect in the code. §5 (docs/design/scheduling-and-config.md, "Overlap policy" and the scheduler paragraph) says "a skip is said in the daemon's log, never queued", "A skipped run records no operation; the daemon's log says why", and "The start page lists each plan with its planned run." Runs skipped for an unmet condition (AC power) or for location rules are said only in the log too.
Proposal
Show the plan's most recent skipped scheduled run, with its time and reason, until the plan's next run starts. For example: "The scheduled run at 7:00 PM was skipped: the last run was still going." It should appear on the plan's page and in the start page's plan list, at least.
Questions for the design:
- Where the fact lives:
PlanSchedulealready holds per-plan state (next_run,last_success, …). One field there, "last skipped scheduled run: when, why", would keep "a skip records no operation" true without adding a newOperationstatus. - Which skips count: the overlap policy, unmet conditions (AC power), and location rules that don't hold. One reason code each, through
l10n, never core sentences. - When it clears: at the plan's next run start (any trigger), or only at its next success.
- Notifications: the default is no, since a skip isn't a failure. Maybe an opt-in event later.
- API and MCP: surface it in the plan's response so
list_plansand the CLI can show it too.
The user can already avoid this case with overlap = "queue", but that doesn't make a skip visible when one happens.
Acceptance
- A scenario: given an hourly plan whose manual run is still going at the hour, when the scheduled run comes due, then the plan shows that its scheduled run was skipped, with the time and the reason, and that clears when the plan's next run starts.
- The design's §5 text and a §16 decision are updated in the same change.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 56m
- Merged PRs (30d)
- 349
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nledford/Ladderback
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
nledford/Ladderback#809 ·
Maintainers usually reply within 1 day
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nledford/Ladderback#759 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nledford/Ladderback#746 ·
Maintainers usually reply within 1 day
-
enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nledford/Ladderback#745 ·
Maintainers usually reply within 1 day
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nledford/Ladderback#647 ·
Maintainers usually reply within 1 day
All issues in nledford/Ladderback
Similar issues
-
benchmark-review
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
area:filesystem bug need-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Captions panel does not offer to show an existing transcriptPossibly taken @thedavidweng claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
CapSoftware/Cap#4276 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
libracoder/kiri#364 ·
Maintainers usually reply within 1 day