Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Next retry delay should not be bounded by retry policy MaximumInterval #6063

Merged
merged 1 commit into from
Jun 5, 2024

Conversation

gow
Copy link
Contributor

@gow gow commented Jun 4, 2024

What changed?

When an activity specifies next_retry_delay in the application failure, we should be ignoring the max interval set in the retry policy. This PR allows it.

Why?

The intention of the application here is to override the retry policy and customize the next attempt time.
https://github.com/temporalio/api/blob/5b356b506e0b86ba26dc6f795bfb011eeb4dfa6e/temporal/api/failure/v1/message.proto#L49

How did you test it?

Added unit test.

Potential risks

N/A

Documentation

N/A

Is hotfix candidate?

No

@gow gow requested a review from a team as a code owner June 4, 2024 21:52
@gow gow merged commit 7708a7c into main Jun 5, 2024
42 checks passed
@gow gow deleted the cg_next_retry_delay branch June 5, 2024 17:33
stephanos pushed a commit that referenced this pull request Jun 13, 2024
#6063)

When an activity specifies `next_retry_delay` in the application
failure, we should be ignoring the max interval set in the retry policy.
This PR allows it.

The intention of the application here is to override the retry policy
and customize the next attempt time.

https://github.com/temporalio/api/blob/5b356b506e0b86ba26dc6f795bfb011eeb4dfa6e/temporal/api/failure/v1/message.proto#L49

Added unit test.

N/A

N/A

No
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants