chore(release): v0.6.17 — detached run_workflow dispatch fix#283
Merged
Conversation
…run_workflow dispatches The detached 'workflow run' / run_workflow path bootstraps a Running record then re-attaches a workflow_runner via 'workflow run --sync --workflow-id <id>'. workflow_execute_request_for_existing() built that request with all subject fields None (workflow_id only), so the runner plugin could not resolve subject context and workflow/execute failed (exit 1) — every detached dispatch sat Running then got zombie-cancelled. Only this reattach path was affected: the queue/trigger path carries the subject via build_runner_command, and the --sync --task-id path passes task_id directly (both work). Populate task_id/requirement_id from the persisted record's subject, mirroring the proven fresh-dispatch request. Adds a regression test.
Includes: detached run_workflow / 'animus workflow run' now dispatches — the reattach execute request carries the subject so the runner plugin can resolve subject context (was workflow_id-only → workflow/execute failed).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
What
Fixes the kernel bug where detached `animus workflow run` / MCP `run_workflow` never dispatch a runner — the workflow sits `Running` then gets zombie-cancelled.
Root cause
The detached path bootstraps a `Running` record then re-attaches a workflow_runner via `workflow run --sync --workflow-id `. `workflow_execute_request_for_existing()` built that `workflow/execute` request with all subject fields `None` (only `workflow_id`), so the runner plugin could not resolve subject context and `workflow/execute` failed (exit 1).
Only this reattach path was affected:
Fix
Populate `task_id`/`requirement_id` from the persisted record's subject, mirroring the proven fresh-dispatch request. Adds a regression test.
Verification
🤖 Generated with Claude Code