fix: report workflow errors that end at pause gates#142
Merged
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.
Summary
Workflow failures could become invisible when graph routing ended at a pause gate. The worker suppressed all paused results, even when the invocation had produced a new
last_error. Bug triage and task-takeover triage also returnedtriage_checkfor retryable failures, but their graph routers omitted that destination and silently fell through totriage_gate.Changes
last_erroreven when the final workflow state is pausedtriage_checktriage_checkThe shared reporting fix also covers PRD, spec, epic, and task publishing errors that produce a new error before reaching an approval gate.
Validation
Context
Discovered while running AISOS-2157: a Vertex configuration failure ended at
triage_gatewithlast_error, but no Jira error comment was posted.