fix(docs): prioritize interrupt check in SQL agent HITL example #1885
+3
−3
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.
Overview
check for interrupt before messages to ensure interrupts are not skipped when both keys exist in the stream step.
Type of change
Type: Fix bug
Related issues/PRs
Checklist
docs devsrc/docs.jsonif neededAdditional notes
Problem
The current SQL agent human-in-the-loop example checks for
messagesbefore__interrupt__in the stream loop:This creates a potential bug: if a stream step contains both messages and interrupt keys simultaneously, the interrupt handling block will never execute due to the elif condition.
Solution
Reorder the condition checks to prioritize interrupt detection:
This ensures that interrupts are always detected and handled correctly, even when messages are present in the same step.