fix(cloudflare): Set conversation id independent of session name - #22958
Open
JPeer264 wants to merge 1 commit into
Open
fix(cloudflare): Set conversation id independent of session name#22958JPeer264 wants to merge 1 commit into
JPeer264 wants to merge 1 commit into
Conversation
JPeer264
requested review from
andreiborza and
mydea
and removed request for
a team
August 3, 2026 12:48
JPeer264
force-pushed
the
jp/conversation-id-agents
branch
from
August 3, 2026 12:49
fbf3b66 to
58211d7
Compare
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
Contributor
size-limit report 📦
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The first conversation ID was always the session name of the
useAgent. The issue was that locally, whenname: 'default'was set, the first conversation ID was always set intodefault. After a reset withclearHistorya UUID v4 got assigned and then correctly set into a new bucket.This could potentially also happen on DO hibernations where the cached
__sentryConversationIdgot reset (which is now a Symbol). To prevent this from happening on hibernations the conversation ID is now stored in the DO as__SENTRY_AGENT_CONVERSATION_ID__.Also there was an issue where a manual
Sentry.setConversationId()within aonChatMessagewas not properly overridden, theAGENT_APPLIED_CONVERSATION_ID_SYMBOLmakes sure, that the conversation ID can be overridden by the user if they wish for it.