# SIMPLE way to restart flows within Node-Red

**URL:** <https://discourse.nodered.org/t/simple-way-to-restart-flows-within-node-red/47989>\
**Category:** General\
**Created:** [3 July 2021 20:11 UTC](https://discourse.nodered.org/t/simple-way-to-restart-flows-within-node-red/47989 "2021-07-03T20:11:38Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [4 July 2021 18:23 UTC](https://discourse.nodered.org/t/simple-way-to-restart-flows-within-node-red/47989/14 "2021-07-04T18:23:50Z")

</div>

You can catch the alexa node error/s using the catch node, and reinitialise the alexa authorization.  
There is a example of how to initialise the authenication in the read me help info.  
(this answer assumes you are using one of the alexa remote2 forks)  
here's a link to a thread that talks about [alexa node issues.](https://discourse.nodered.org/t/alexa-remote2-stops-talking/32931)

---

_[View the full topic](https://discourse.nodered.org/t/simple-way-to-restart-flows-within-node-red/47989)._