temporalio / temporalio/features
[Feature Request] Auto timeout activity after heartbeat timeout
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
When activity has valid heartbeat timeout configured, but activity code never bother to do heartbeat (due to bug or edge cases), in that case, after timeout server would schedule a retry, and the old activity should exist. However, currently the context is only cancelled after activity try to heartbeat. (At least sdk-go behavior this way.)
Describe the solution you'd like
SDK should set a heartbeat timeout, and cancel the context so activity could fail fast if it does not try to heartbeat at all.
Additional context
Contributor guide
No contributing guide indexed for this repository
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
No specific file or test is named. Start by examining the repository's behavior and history compatibility tests for activity heartbeat timeouts, then compare the SDK-Go behavior described in the issue with the expected timeout and cancellation behavior across SDKs; done means the compatibility tests cover cancellation when no heartbeat is attempted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100