fix(worker): prevent manual dispatch run leakage - #280
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: Comment |
outof-place
force-pushed
the
fix/run-dispatch-leak-p2
branch
from
August 28, 2026 06:20
5a079cc to
9bb842b
Compare
outof-place
marked this pull request as ready for review
August 28, 2026 06:57
|
Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits. |
This was referenced Aug 28, 2026
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.
Defect
A coordinator-consented manual MCP ticket dispatch reserves the subject and moves the ticket into the shared
Aicolumn. The Jira webhook and poll pickup path also treat that column as default-workflow enrolment, so releasing the manual run's claim while the ticket remained there allowed unconsented default runs to start on consecutive pickups. This was observed in production aswrun_01KZYCWTYMDN6EVNV7BETD71XMandwrun_01KZYD0FDD1DBT6YYK4GXMXD9J.Invariant and approach
One coordinator-consented manual dispatch causes at most that one consented run. The existing manual subject reservation remains the immediate auto-pickup marker; this change adds owner-fenced withdrawal from
Aibefore amanual_ticketclaim can be released on natural terminal reconciliation or operator cancellation. If Jira withdrawal cannot be confirmed, ownership is retained for retry, and a workflow-selected destination outsideAiis preserved. The manual-dispatch preflight now states that manual ownership suppresses automatic pickup until the run withdraws or moves the ticket.Focused verification
No full local suite was run; CI provides breadth.
Generated by an AI coding agent via Orca.