temporalio / temporalio/features
[Feature Request] SDK workers should not intentionally time out failed workflow tasks if server supports backoff
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
At the moment the SDK worker will intentionally timeout a workflow task instead of failing it in case the attempt is greater than 1. This is how the system slows down failing workflow tasks and is important for system resilience.
We could add a server capability and disable the worker timeout behavior based on it.
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 tracing how the SDK worker handles failed workflow tasks after the first attempt and how server capabilities are exposed. Determine where the capability should control intentional timeout versus failure behavior, then add compatibility coverage showing both server-supported backoff and older-server behavior.
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