temporalio / temporalio/sdk-java
Local Activity Execution should stop making attempts if Workflow Task or subsequent heartbeat fails
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Is your feature request related to a problem? Please describe.
Right now Local Activity Execution is not aware of the lifecycle of the Workflow Task that started this execution.
If Workflow Task (or one of its subsequent heartbeats) is already failed, Local Activity will continue execution.
If there is no scheduleToClose timeout set or scheduleToClose is long, such an orphan local activity can retry for a long time.
Describe the solution you'd like
Local Activity Execution should stop making new attempts if the workflow task caused this execution is failed.
Additional context
This task should likely be coupled with the implementation of Local Activity Cancelations: #1303
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 by tracing the Local Activity Execution lifecycle and how it observes Workflow Task failures and subsequent heartbeats. Review the related Local Activity Cancelations issue #1303. The work is done when failed workflow tasks prevent further local activity attempts, including retries, without relying only on scheduleToClose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100