temporalio / temporalio/temporal
Workflow Reset: add logic of determining the reset point to the service
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
tctl workflow reset supports reset_type argument. The ResetWorkflowExecution gRPC API accepts only workflow_task_finish_event_id. So all the logic of finding reset point resides in the tctl. This makes the logic not reusable when SDKs invoke reset operation directly.
Describe the solution you'd like
Move logic of finding reset point to the service by adding reset_type argument to ResetWorkflowExecutionRequest.
Contributor guide
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 the tctl workflow reset command and the ResetWorkflowExecution gRPC API, then inspect ResetWorkflowExecutionRequest and the existing reset_type handling. The change is complete when reset-point selection is performed by the service and SDK callers can provide reset_type through the request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grpc
- Domain
- api, backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100