temporalio / temporalio/features
[Feature Request] Always flush completed local work when nearing the workflow task timeout
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
In sdk-core, when a local activity completes, it will not flush progress and issue a workflow task heartbeat until it has successfully activated the workflow notifying it of the completion.
In some edge cases, like this scenario:
WFT timeout is 3 seconds, local activity takes 2 seconds, responding to last activation takes 1.1 seconds.
Here, the workflow task will timeout losing the local activity progress.
If these timing are consistent enough, the workflow will be stuck and not be able to progress.
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
Start by locating the sdk-core path that handles local activity completion, progress flushing, workflow task heartbeats, and workflow activation. Reproduce the 3-second timeout scenario described in the issue, then verify that completed local activity progress is flushed before activation can cause the workflow task to time out.
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
- 35/100