temporalio/sdk-java

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

Open

#1,727 opened on Mar 31, 2023

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Java (231 forks)auto 404
good first issue

Repository metrics

Stars
 (421 stars)
PR merge metrics
 (PR metrics pending)

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

HelloLocalActivity.java.zip

Specifications

  • Version:
  • Platform:

Contributor guide

Research direction
Inspect the retry policy handling for local activities in the SDK Java codebase. Compare with normal activities to identify where MaximumAttempts=0 is not treated as unlimited retries.
Tech stack
java
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaTemporal SDK
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70