Associate consumed input with its conversation turn - #44
Merged
Merged
Conversation
longquanzheng
marked this pull request as ready for review
September 25, 2026 04:01
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.
Summary
input_consumedactivity with the durable user turn created in the same Dex commitUser impact
The conversation no longer starts with a misleading
Historical activitycard containingConsumed 1 queued user message.. Existing unanchored events are hidden, while new events carry the durable user message sequence and belong to the correct turn.Validation
make checkmake check-flow-definitionDEX_FLOW_SERVICE_ADDRESS=127.0.0.1:8801 INTEGRATION_TEST_RUN='^(TestAgentFlowDurabilityIntegration|TestAgentBatchSteeringIntegration)$' make test-dex-integrationDEX_FLOW_SERVICE_ADDRESS=127.0.0.1:8801 make test-full-stack-e2e(20 passed)