Repository navigation
Conversation
A channel tells its listeners that a source they consume has moved, without carrying the data. These RPCs let a client notify, poll, describe and manage the callback listeners of a channel.
This was referenced Oct 3, 2026
Owner
Author
|
Paused per the 2026-10-05 design review (the decision record is on the proposal page, section 14). Resumes in phase 2 with the CHASM notification work. The branch stays as a pin. |
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.
This PR adds the notification channel service to
WorkflowService.What changed?
temporal/api/notification/v1package withNotification,ChannelListener,WorkflowListenerandChannelKind.SignalWorkflowExecution:NotifyChannel,RegisterChannelListener,UnregisterChannelListener,PollChannelandDescribeChannel, with their request and response messages.executionon a request picks the linked one.temporal-resource-idtochannel:<name>, like the other RPCs set theirs. Every channel request names a channel, andexecutiononly narrows it to a linked owner.openapi/regenerated.Part of AI-198 (epic AI-37).
Why?
A writer that wants to wake its consumers today has to know each one and Signal it, and every wake-up lands in the consumer's History. A channel flips that around. The writer names a channel, not an addressee, and never learns who listens. Callbacks get invoked and clients long poll. Workflows come in the next PR.
How did you test it?
Link to a test plan if any -
make buf-lint,make api-linterandmake http-api-docsare clean. I also ranmake go-grpcand built the output in a scratch module, and it builds and vets fine. The server, Core, Python and CLI PRs in the series hit these RPCs end to end against a fork server.