fix: queen bee multiple response error resolved#5962
Open
AryanNandanwar wants to merge 1 commit intoaden-hive:mainfrom
Open
fix: queen bee multiple response error resolved#5962AryanNandanwar wants to merge 1 commit intoaden-hive:mainfrom
AryanNandanwar wants to merge 1 commit intoaden-hive:mainfrom
Conversation
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
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.
Description
Queen Bee was sometimes posting multiple, near-duplicate replies for a single user message in the web UI. Each Queen streaming event was converted into a ChatMessage with a unique id. This change gives Queen streaming events a stable per‑execution message ID, so all snapshots for one run collapse into a single chat bubble.
Type of Change
Related Issues
Fixes #5759
Changes Made
Updated handleSSEEvent in core/frontend/src/pages/workspace.tsx so that:
For Queen events (stream_id === "queen") of type client_output_delta or llm_text_delta, we override the auto-generated ChatMessage.id with a stable ID of the form queen-stream-<execution_id | node_id>.
This causes upsertChatMessage to update the same Queen message in place instead of appending new messages for each snapshot.
Left worker behavior unchanged (workers still get distinct message IDs per iteration, so each step remains a separate bubble).
Testing
Checklist