Skip to content

💥 Update documention of current_retry_interval and next_attempt_schedule_time#840

Open
dandavison wants to merge 2 commits into
mainfrom
activity-current-retry-interval
Open

💥 Update documention of current_retry_interval and next_attempt_schedule_time#840
dandavison wants to merge 2 commits into
mainfrom
activity-current-retry-interval

Conversation

@dandavison

Copy link
Copy Markdown
Contributor

What changed?

Why?
The current behavior of WFA was deemed to be a bug and changed in temporalio/temporal#11203

// failure and when the next attempt will become available to worker poll requests. Set only
// during retry backoff, i.e. when an activity is currently waiting for a retry, and the next
// activity task has not yet become available to worker poll requests. Null at all other times,
// including when paused and during start delay. This is calculated from the active retry policy,

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe when paused, the server still returns the stale future next_attempt_schedule_time and current_retry_interval. So I think we should clear those during pause for server

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks updated the server PR to do that.

@dandavison
dandavison force-pushed the activity-current-retry-interval branch 2 times, most recently from fd3cd76 to 108be42 Compare July 24, 2026 00:29
@dandavison
dandavison force-pushed the activity-current-retry-interval branch from 108be42 to 26ad7c3 Compare July 24, 2026 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants