Recovery procedure for flow that keeps erroring

#1

Is there a standard recovery procedure if you accidentally cause a flow that keeps crashing the console before you can fix it and deploy again? I assume that his is why the backup flow is created but I can't seem to figure out how to use it. Sorry for the newbie question.

0 Likes

#2

You can rename the failing flow and rename the backup to be the live flow.

If all else fails, you should be able to rename the live flow, restart - creates a blank flow. Copy the text from the live flow and import it back in, delete what you think is causing the issue before deploying changes.

0 Likes