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

inconsistency on MaximumAttempts attribute between local activities and "normal" activities #1727

Open
antmendoza opened this issue Mar 31, 2023 · 0 comments · May be fixed by #2257
Open

inconsistency on MaximumAttempts attribute between local activities and "normal" activities #1727

antmendoza opened this issue Mar 31, 2023 · 0 comments · May be fixed by #2257

Comments

@antmendoza
Copy link
Member

Expected Behavior

setting setMaximumAttempts=0 (or not setting any value, default = 0) for local activities should make the activity retry forever.

I expect the same behavior as "normal" activities, where MaximumAttempts=0 implies retry forever.

Actual Behavior

when MaximumAttempts is set to 0, local activities do not retry

Steps to Reproduce the Problem

HelloLocalActivity.java.zip

Specifications

  • Version:
  • Platform:
@Spikhalskiy Spikhalskiy added this to the 1.20.0 milestone Apr 20, 2023
@Spikhalskiy Spikhalskiy self-assigned this Apr 20, 2023
ghaskins added a commit to ghaskins/temporal-sdk-java that referenced this issue Oct 7, 2024
…ot set or setMaximumAttempts(0)

Setting setMaximumAttempts=0 (or not setting any value, default = 0) for local activities should make the activity retry forever.

This is currently broken because the logic treats both no policy set and a policy with all default values (including MaxiumAttempts = 0)
as abort conditional.  What should happen (at least according the doc and to align with normal activities) is that no policy set should
be processed according to the default values of the retry policy, which includes unlimited retries when the MaxiumAttempts = 0.

Fixes temporalio#1727

Signed-off-by: Greg Haskins <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants