# Recovery procedure for flow that keeps erroring

**URL:** <https://discourse.nodered.org/t/recovery-procedure-for-flow-that-keeps-erroring/4776>\
**Category:** General\
**Created:** [12 November 2018 03:19 UTC](https://discourse.nodered.org/t/recovery-procedure-for-flow-that-keeps-erroring/4776 "2018-11-12T03:19:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jewendt](https://avatars.discourse-cdn.com/v4/letter/j/3ab097/32.png) [@jewendt](https://discourse.nodered.org/u/jewendt)\
**Post date:** [12 November 2018 03:19 UTC](https://discourse.nodered.org/t/recovery-procedure-for-flow-that-keeps-erroring/4776/1 "2018-11-12T03:19:29Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [12 November 2018 07:04 UTC](https://discourse.nodered.org/t/recovery-procedure-for-flow-that-keeps-erroring/4776/2 "2018-11-12T07:04:56Z")

</div>

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.