Skip to content

fix: Orchestrator - Fixed executions remaining stuck in WAITING_FOR_UPSTREAM status forever when an upstream queued execution node failed to launch with SYSTEM_ERROR - #316

Merged
Ark-kun merged 1 commit into
masterfrom
ycq/fix-queued-failure-waiting-forever
Aug 8, 2026
Merged

Conversation

@yuechao-qin

@yuechao-qin yuechao-qin commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Closes #315

Copy link
Copy Markdown
Collaborator Author

@yuechao-qin
yuechao-qin marked this pull request as ready for review August 7, 2026 18:19
@yuechao-qin
yuechao-qin requested a review from a team August 7, 2026 18:19
@yuechao-qin
yuechao-qin requested a review from Ark-kun as a code owner August 7, 2026 18:19
@Ark-kun Ark-kun changed the title fix: Queued-execution failure strands the downstream subtree in WAITING_FOR_UPSTREAM forever fix: Orchestrator - Fixed executions remaining stuck in WAITING_FOR_UPSTREAM status forever when an upstream queued execution node failed to launch with SYSTEM_ERROR Aug 8, 2026
@Ark-kun
Ark-kun merged commit 41dcb69 into master Aug 8, 2026
7 checks passed
@Ark-kun
Ark-kun deleted the ycq/fix-queued-failure-waiting-forever branch August 8, 2026 02:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: Queued-execution failure strands the downstream subtree in WAITING_FOR_UPSTREAM forever

2 participants