Skip to content

fix: Orchestrator - Only setting execution node status to CANCELLED after the container execution is terminated - #241

Merged
Ark-kun merged 1 commit into
masterfrom
ark/fix-Orchestrator---Only-marking-execution-node-as-CANCELLED-after-the-container-execution-is-terminated
Aug 8, 2026
Merged

fix: Orchestrator - Only setting execution node status to CANCELLED after the container execution is terminated#241
Ark-kun merged 1 commit into
masterfrom
ark/fix-Orchestrator---Only-marking-execution-node-as-CANCELLED-after-the-container-execution-is-terminated

Conversation

@Ark-kun

@Ark-kun Ark-kun commented May 16, 2026

Copy link
Copy Markdown
Contributor

Fixes: #240

…fter the container execution is terminated

Fixes: #240
@Ark-kun Ark-kun self-assigned this May 16, 2026
@Ark-kun
Ark-kun merged commit c940169 into master Aug 8, 2026
6 checks passed
@Ark-kun
Ark-kun deleted the ark/fix-Orchestrator---Only-marking-execution-node-as-CANCELLED-after-the-container-execution-is-terminated branch August 8, 2026 02:40
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: Orchestrator - Execution node status can change from CANCELLED to SUCCEEDED

2 participants