Cron jobs not firing for secondary multiplex profiles
Cluster 69377 · cron. Data as of
Nothing open on GitHub. Fix merged in #70646 on 24 Jul 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 #70646. 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.
A bug where the single gateway only ticks the default profile's cron store under multiplex_profiles, causing cron jobs registered in secondary profiles to never fire. The members include a bug report and an associated fix.
Open issues0
Open PRs0
Fixes on record
-
#70646 fix(cron): tick every served profile's cron store under multiplex_profiles (#69377)
files:
cron/jobs.py,cron/scheduler_provider.py,gateway/run.py,tests/cron/test_scheduler_provider.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#69529 fix(cron): tick every served profile's cron store under multiplex_profiles (#69377) · merged via another change →
#70646
Closed issues · 1
- Closed#69377multiplex_profiles: cron jobs registered in a secondary profile's store never fire — the single gateway only runs the default profile's ticker
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
- Subsystem
- cron
- Merged PRs
- #70646
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 24 Jul 2026