Repository navigation
Add nexus caller timeouts - #695
Merged
Merged
Conversation
bergundy
force-pushed
the
nexus-caller-timeouts
branch
from
January 12, 2026 23:58
dc6822f to
44dec06
Compare
This was referenced Jan 13, 2026
Quinn-With-Two-Ns
approved these changes
Jan 13, 2026
cretz
approved these changes
Jan 13, 2026
cretz
left a comment
cretz
left a comment
Contributor
There was a problem hiding this comment.
I assume like child workflows, none of these timeouts are required
pdoerner
approved these changes
Jan 13, 2026
Member
Author
See the comment in code: |
bergundy
added a commit
to temporalio/temporal
that referenced
this pull request
Jan 13, 2026
## Overview This commit implements two new granular timeout types for Nexus operations, allowing callers to have fine-grained control over different phases of operation execution: - **Schedule-to-Start Timeout**: Maximum time to wait for an operation to be started (or completed if synchronous) by the handler - **Start-to-Close Timeout**: Maximum time to wait for an asynchronous operation to complete after it has been started These timeouts complement the existing **Schedule-to-Close Timeout** to provide better control and diagnostics for Nexus operation execution. See the corresponding API PR: temporalio/api#695.
bergundy
added a commit
to temporalio/sdk-go
that referenced
this pull request
Feb 12, 2026
## Overview Implements two new granular timeout types for Nexus operations, allowing callers to have fine-grained control over different phases of operation execution: - **Schedule-to-Start Timeout**: Maximum time to wait for an operation to be started (or completed if synchronous) by the handler - **Start-to-Close Timeout**: Maximum time to wait for an asynchronous operation to complete after it has been started These timeouts complement the existing **Schedule-to-Close Timeout** to provide better control and diagnostics for Nexus operation execution. See also temporalio/api#695 and the corresponding server PR: temporalio/temporal#9010.
stephanos
pushed a commit
that referenced
this pull request
Mar 10, 2026
**What changed?** Add ScheduleToStart and StartToClose timeouts for Nexus operations. **Why?** Give callers more control over timeouts of the various operation lifecycle stages. **Server PR** temporalio/temporal#9010
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
4 participants
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?
Add ScheduleToStart and StartToClose timeouts for Nexus operations.
Why?
Give callers more control over timeouts of the various operation lifecycle stages.
Server PR
temporalio/temporal#9010