temporalio / temporalio/features
Expose attempts in `ActivityFailure`
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.
Today there's no way in a workflow to know how many attempts an activity made before failing.
This has come up in community slack where a user wanted to report this number from a workflow.
Describe the solution you'd like
Expose an attempts field in ActivityFailure, the SDK has this information in the ActivityTaskStarted event.
The field should be populated in case the activity ended up as failed or canceled.
Per-SDK Tickets
- Go -
- Java -
- Core -
- TypeScript -
- Python -
- .NET -
- PHP -
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 with ActivityFailure and the ActivityTaskStarted definition in temporal/api/history/v1/message.proto, which contains the attempts information. Trace how that value is exposed across the listed Go, Java, Core, TypeScript, Python, .NET, and PHP SDK tickets; done means failed or canceled activities report their attempt count.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100