Update API: preserve update request after reset like signal request

[dhiaayachi]

Is your feature request related to a problem? Please describe. If reset point is before the update request, the update request will be lost after reset. This is not expected in many use cases. Similar to signal, update requests are trigger from external actions like human actions, and not recoverable like activity (with idempotency).

Describe the solution you'd like Similar to reset, by default it should preserve all the update requests after reset points to re-apply to the new run. And provide an option to skip the re-apply.

Describe alternatives you've considered NA

Additional context https://temporalio.slack.com/archives/CTQU95E84/p1681514936017749

[dhiaayachi]

Thank you for reporting this issue!

This is a feature request and we appreciate you bringing it up.

Currently, Temporal doesn't automatically preserve and re-apply update requests after a reset. However, you can work around this by manually tracking the updates in your workflow and re-applying them after the reset. You can use a queue or a list to store the updates. When the workflow is reset, you can iterate over the queue and re-apply the updates.

We are considering adding this feature to Temporal in the future.

Let me know if you have any other questions!

[dhiaayachi]

Thanks for reporting this. This feature is being considered for future versions of Temporal. As a workaround, you can schedule a new workflow to reapply the updates, but this may lead to a higher latency.

[dhiaayachi]

Thank you for reporting this issue. This is a known issue and we are actively working on addressing it. Please refer to Temporal Failures for more information.