Conversation
A parked Run has no open Workflow Task, so the server dispatches a query on a task of its own and Core allows nothing beside the answer there. The instance still reported the registered wait set, Core refused the completion, and the query timed out.
The id is Core's, and nothing in this file said where it is defined, so a rename over there would be found by a failing query rather than by grep.
This was referenced Oct 3, 2026
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.
This PR fixes queries against a workflow parked on an external stream.
What changed?
_emit_external_stream_commandsreturns before it adds the stream snapshot, the progress marker or the channel report._LEGACY_QUERY_IDis held in step with Core'sLEGACY_QUERY_ID.Part of AI-198 (epic AI-37).
Why?
A parked run has no open Workflow Task, so the server sends a query on a task of its own. Core allows nothing beside the answer on that task. The instance still added the wait set it had registered, so Core refused the completion and the query timed out. That activation ran no workflow code, so there's nothing new to report anyway.
How did you test it?
Link to a test plan if any -
Without the fix, the new case times out. With it, the case and the whole external stream suite pass on the dev server, and
poe lintis clean.