Cronjob deliver=origin thread context preservation (Telegram)
Cluster 1219 · cron. Data as of
Nothing open on GitHub. Fix merged in #1437 on 15 Mar 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #1437. 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.
The members consist of one bug report and three fix-titled items, all concerning cronjobs using 'deliver: origin' and whether thread context is preserved. The bug report specifically mentions Telegram; the others do not state a platform in their titles.
Open issues0
Open PRs0
Fixes on record
-
#1437 fix: preserve thread context for cronjob deliver=origin
files:
gateway/run.py,tests/gateway/test_session_env.py,tests/tools/test_cronjob_tools.py,tools/cronjob_tools.py
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#1219[Bug]: Cronjob 'deliver: origin' doesn't preserve Telegram thread context
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.50: 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
- #1437
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 15 Mar 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.