Overview
Users could sometimes see 2 workflows created in the target location when loading workflows from a snapshot. This happened when duplicate workflow requests were sent at the same time, causing one workflow to remain in Processing while another completed successfully.
What’s changed
We've added a locks to ensure that when a workflow is loaded from a snapshot only 1 workflow is created for the same origin and location. This prevents duplicate workflows and avoids extra workflows getting stuck in Processing state.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article