temporalio / temporalio/sdk-java
inconsistency on MaximumAttempts attribute between local activities and "normal" activities
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
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
Specifications
- Version:
- Platform:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the local activity retry handling and compare its MaximumAttempts behavior with normal activities, using the attached HelloLocalActivity.java reproduction. Verify the default and explicit value of 0, then confirm that a failing local activity retries forever while matching normal activity semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100