You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Running reset-batch on a large number of workflows can be problematic, as the resetting is done within the CLI and not within an internal workflow. This can be a risk within remediation of an incident because we are relying on the connection between a laptop and the temporal server which could have several failures and/or rate-limiters.
Describe the solution you'd like
It would be great if reset-batch was ran as an internal workflow within Temporal, like some of the other commands. This would help ensure reliability and improve remediation speed in the case of an incident with a large number of workflows.
Additional context
Also posted another issue from this particular incident at #239.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Running reset-batch on a large number of workflows can be problematic, as the resetting is done within the CLI and not within an internal workflow. This can be a risk within remediation of an incident because we are relying on the connection between a laptop and the temporal server which could have several failures and/or rate-limiters.
Describe the solution you'd like
It would be great if reset-batch was ran as an internal workflow within Temporal, like some of the other commands. This would help ensure reliability and improve remediation speed in the case of an incident with a large number of workflows.
Additional context
Also posted another issue from this particular incident at #239.
The text was updated successfully, but these errors were encountered: