Repository navigation
Conversation
General (multi-session) workers need to send their address on polls so the server can bind a workflow session to the worker when a task starts on it, including tasks taken from the normal queue. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Shivs11
commented
Nov 17, 2026
| oneof admission { | ||
| // If specified, the worker only polls for work belonging to its session. | ||
| SingleSessionOptions single_session = 1; | ||
| // If specified, the worker can serve multiple sessions at once. |
Member
Author
There was a problem hiding this comment.
i could be missing something, but in my head a general session worker == multi-session worker since it can serve multiple workflows-as-sessions (which is why i scraped off using 'GeneralSessionOptions' and made this)
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.
What changed?
Stacked on #885. Adds a second
admissionmember toWorkerSessionOptions:oneof admission { SingleSessionOptions single_session = 1; MultiSessionOptions multi_session = 2; } message MultiSessionOptions { // Set by the SDK to the worker's sticky queue name; not user-configurable (for now). string worker_address = 1; }Why?
General (multi-session) workflow sessions need to recover when their worker dies. When the session's next task starts on another worker, including a task taken from the normal queue, the server binds the session to that worker and reschedules pending session work onto its sticky queue. To do that, the server needs the worker's address on the poll. Today, general workers send only
WorkerSessionOptions{}on sticky polls.Breaking changes
None on released APIs (experimental, unreleased).
Server PR
Follows; server-side start binding is still in design.