Workflows: Implement task execution ids
Open
- Dominant language
- Go
- Stars
- 479
- Forks
- 187
- PR merge metrics
- No merged PRs in 30d
Description
Task execution ids must be unique and can be used for idempotency, task state or error handling.
java-sdk already introduced it [task execution ids](https://github.com/dapr/durabletask-java/commit/85e0cac3f02416ab52a25f08d0c9a3691cfc38f5) and [here](https://github.com/dapr/java-sdk/pull/1352)
Contributor guide
Research direction
Start by reviewing the linked Java SDK task execution ID implementation, then locate the corresponding workflow and task APIs in this Go SDK. Done means task execution IDs are unique and available for idempotency, task state, or error handling in the Go implementation, with matching tests added where the existing workflow tests cover these behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100