Repository navigation
fix: run an Automation only once when its Session is opened afterwards - #2089
Merged
Merged
Conversation
Douglasymlai
marked this pull request as ready for review
October 22, 2026 21:48
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.
Pull Request
Related Issue
N/A — maintainer-directed repair; no linked issue required for this PR.
Description
Problem
Background Automations used a random task ID instead of the durable queue request ID, leaving the original request available for another admission when its Session opened.
Change
Start the background task with the existing queue request ID. The backend's admission transaction then marks that exact request admitted and deduplicates retries; terminal-state handling can admit the next execution. Updated against current main.
Testing Evidence (REQUIRED)
79 focused frontend tests and 6 durable queue tests passed, covering deterministic identity, re-entrant dispatch, subsequent execution admission, and request deduplication. Type checking, focused ESLint/Prettier and git diff --check passed.
No new UI primitives, tokens or design exceptions. A full scheduled Automation in the packaged app was not run; remote CI follows the updated head.
Automated checks only; manual app testing is pending.
What is the purpose of this pull request?
Contribution Guidelines Acknowledgement