Cron bot-chat delivery uses wrong profile environment
Cluster 117220. Data as of
Nothing open on GitHub. Fix merged in #117619 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 #117619. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #117619. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where cron bot-chat deliveries to another profile incorrectly run using the destination profile's environment (credentials and authorization) instead of the sender's. The cluster covers the bug report and associated fixes.
Open issues0
Open PRs0
Fixes on record
-
#117619 fix(cron): bot-chat delivery to another profile runs with the destination's environment, not the sender's (#117220, salvage #117221)
files:
cron/scheduler_delivery.py,tests/cron/test_bot_chat_delivery_child_env.py,website/docs/user-guide/features/cron.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#117221 fix(cron): a bot-chat delivery builds its child env for the DESTINATION profile, not the sender · merged via another change →
786c0e3,#117619
Closed issues · 1
- Closed#117220[Bug]: cron `deliver: bot-chat:<other profile>` runs the destination's turn with the sending gateway's environment (credentials and authorization gates included)
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
- #117619
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 20 Sep 2026