fix(web): a new workbench's first message is never dropped (CL-9585) - #1007
Merged
Merged
Conversation
TheGreatAxios
enabled auto-merge (squash)
September 30, 2026 05:39
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 opening message is parked client-side when the workbench is created; the workbench page shows it as a pending bubble and sends it as soon as the agent is live.
Past 60s without a live agent, or on a send error, it stays visible with a Retry and is only cleared once the send succeeds.
createWorkbench no longer skips the send; the unused opening-message failure stage is removed.
Resolves CL-9585