temporalio / temporalio/temporal
Support reset starting from an activity of a specific type.
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.
From a support topic::
The other day we had this issue where the team responsible for service C told us to rerun the request again since they were presenting issues and the 200 OK we got was a false positive.
So we did it manually, They were just a few requests affected so we could do it without problems. But now we wonder what would happen when we got 1000 affected requests and we had to do it again.
That’s why we were trying to find a way to get (in a programmatic way) the event id to use in the CLI.
Describe the solution you'd like
Support reset that accepts an activity type and status (OK, Failed, Any) and resets workflow from that point. It assumes that reset can recreate the activity task for all activities that completed after the reset point.
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
The issue names no files or tests; start by tracing the existing reset flow and CLI handling for workflow history. Done means supporting an activity type plus OK, Failed, or Any status and recreating activity tasks completed after the selected reset point.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100