# Email-in node occasionally gets stuck fetching

**URL:** <https://discourse.nodered.org/t/email-in-node-occasionally-gets-stuck-fetching/71450>\
**Category:** General\
**Created:** [29 November 2022 13:37 UTC](https://discourse.nodered.org/t/email-in-node-occasionally-gets-stuck-fetching/71450 "2022-11-29T13:37:09Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![hepcat72](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/hepcat72/32/8078_2.png) [@hepcat72](https://discourse.nodered.org/u/hepcat72)\
**Post date:** [29 November 2022 23:52 UTC](https://discourse.nodered.org/t/email-in-node-occasionally-gets-stuck-fetching/71450/15 "2022-11-29T23:52:45Z")

</div>

Well, I tried out the test flow from [this thread](https://discourse.nodered.org/t/restart-flows-using-node-red-api/34632/11). Although it contains an `id` to ostensibly restart just the flow with the supplied `id`, it does restart all flows... The docs don't seem to indicate that this is possible, though one dev in the threads said it needed an overhaul in 2020. I don't suppose the overhaul has happened and the docs are outdated? Either way, I'm going to implement the status-watch suggestion and redeploy via a deadman switch on that status node.

---

_[View the full topic](https://discourse.nodered.org/t/email-in-node-occasionally-gets-stuck-fetching/71450)._