temporalio / temporalio/temporal
Atomic workflow reset & update
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.
- The use case is to reset the workflow to a previous point and immediately sends a update request to update the state.
- Currently, reset & update cannot be applied together. Update can happen milliseconds~second later after reset. There could be a race that when the code rely on the updated state after reset immediately, but the update request is not guaranteed to be applied atomically with reset, resulting in the reset-ed workflow execution continues with the "old" state.
Describe the solution you'd like
Provide a API, preferably something like ResetWithUpdate(...) to reset to a point of event with the update request fulfilled.
Describe alternatives you've considered
Using workflow.Await but the approach comes with extra flags to control the logic flow.
Additional context
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
No files or tests are named. Start by tracing the existing workflow reset and update API entry points, then determine how their state transitions are coordinated. Done means a documented API provides reset and update semantics atomically and tests verify that the reset execution cannot continue with the old state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100