temporalio / temporalio/features
[Feature Request] Expose next retry delay on Application Failure in all SDKs
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
We recently added the ability for an activity to specify the next retry delay on failure via a field on ApplicationFailureInfo.
This needs to be exposed in all SDKs:
- Go - https://github.com/temporalio/sdk-go/pull/1319
- Java - https://github.com/temporalio/sdk-java/issues/1983
- TypeScript - https://github.com/temporalio/sdk-typescript/issues/1349
- Python - https://github.com/temporalio/sdk-python/issues/468
- .NET - https://github.com/temporalio/sdk-dotnet/issues/186
- PHP - https://github.com/temporalio/sdk-php/issues/395
We also need to support this in local activities:
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 the linked Python issue 468 and PHP issue 395, then review the unchecked local-activity support items and their linked SDK/Core issues. Confirm which SDKs still lack the ApplicationFailureInfo retry-delay exposure and local-activity support; done means the remaining checklist items are implemented and verified in their repositories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, php, python, typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100