temporalio / temporalio/features
Expose Workflow cancel cause/reason
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
WorkflowExecutionCancelRequestedEventAttributes has a cause field that should be exposed when workflows receive cancels, and we should additionally expose this as an input when users are issuing cancels from clients or commands
- Python https://github.com/temporalio/sdk-python/issues/764
- TypeScript https://github.com/temporalio/sdk-typescript/issues/1626
- Java https://github.com/temporalio/sdk-java/issues/2414
- .NET https://github.com/temporalio/sdk-dotnet/issues/412
- Go https://github.com/temporalio/sdk-go/issues/1817
- PHP https://github.com/temporalio/sdk-php/issues/567
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 reviewing WorkflowExecutionCancelRequestedEventAttributes and the linked SDK issues for Python, TypeScript, Java, .NET, Go, and PHP. Confirm how each SDK receives workflow cancels and how clients or commands issue them; the work is done when the cause is exposed to workflows and accepted as cancel input across the listed SDKs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, go, java, php, python, typescript
- Domain
- distributed-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100