# NousResearch/hermes-agent · Cron job profile ownership and scope fixes

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #117025. Verify it addresses your case.
- **Recommended:** read PR #117025 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #107666: \[Bug\]: Desktop cron lists jobs with profile=all but saves with the active profile — non-owner scope 404s "Job not found"

## Prior & competing PRs

- **#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)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/web_routers/cron.py`, `tests/hermes_cli/test_web_server_cron_profiles.py`, `website/docs/user-guide/desktop.md`
- **#107670: fix(cron): fall back to owner profile when item scope misses the job**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `#117025`, `#107666`

## Fix status

- Merged to main in PR #117025 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-20`.