Skip to content

fix: queen bee multiple response error resolved#5962

Open
AryanNandanwar wants to merge 1 commit intoaden-hive:mainfrom
AryanNandanwar:feature/bug-fix-5759
Open

fix: queen bee multiple response error resolved#5962
AryanNandanwar wants to merge 1 commit intoaden-hive:mainfrom
AryanNandanwar:feature/bug-fix-5759

Conversation

@AryanNandanwar
Copy link

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

  • Bug fix (non-breaking change that fixes an issue)

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

  • Manual testing performed

Checklist

  • My code follows the project's style guidelines
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: The Queen bee reports the status of a response multiple times.

1 participant