Fix subworkflow invocation tracking#1560
Merged
mvdbeek merged 5 commits intogalaxyproject:masterfrom Aug 18, 2025
Merged
Conversation
52b19e2 to
44b2259
Compare
"paused" isn't a failed job state, so this wouldn't terminate invocation polling in fail_fast mode.
…'failed' failed is not a job state.
3472434 to
58fc42f
Compare
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.
We were skipping subworkflow invocations if the subworkflow invocation hadn't been scheduled yet, and there is no subworkflow_invocation_id on the step state. We now only return a subworkflow invocation as completed if it doesn't have any new steps