Nothing open on GitHub. Fix merged in #117025 on 20 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #117025. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where desktop cron operations used the wrong profile scope for jobs owned by a non-active profile, causing 404 errors, and introduce fixes to follow the job's owning profile for history and actions.
Open issues0
Open PRs0
Fixes on record
-
#117025 fix(cron): Desktop cron run history and per-job actions follow the job's owning profile across the cross-profile list (#115345, salvage #115388)
files:
hermes_cli/web_routers/cron.py,tests/hermes_cli/test_web_server_cron_profiles.py,website/docs/user-guide/desktop.md
1 PR closed without merging
From the close comments: done elsewhere 1
-
#107670 fix(cron): fall back to owner profile when item scope misses the job · done elsewhere →
#117025,#107666
Closed issues · 1
- Closed#107666[Bug]: Desktop cron lists jobs with profile=all but saves with the active profile — non-owner scope 404s "Job not found"
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #117025
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026