# Catch errors during flow deployment

**URL:** <https://discourse.nodered.org/t/catch-errors-during-flow-deployment/33096>\
**Category:** Developing Nodes\
**Created:** [19 September 2020 19:58 UTC](https://discourse.nodered.org/t/catch-errors-during-flow-deployment/33096 "2020-09-19T19:58:45Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)\
**Post date:** [21 September 2020 14:48 UTC](https://discourse.nodered.org/t/catch-errors-during-flow-deployment/33096/9 "2020-09-21T14:48:37Z")

</div>

A [similar issue](https://discourse.nodered.org/t/getting-the-initial-status-of-nodes/22162) arises at startup when a node displays its status before a `status` node is ready to receive it. This can mean that a flow that should be triggered by that status message will not start or that a dashboard item showing the node status may not be correct. The only obvious remedy seems to be giving priority to the `status` and `catch` nodes when the flow is deployed, and I don't know where that stands.

---

_[View the full topic](https://discourse.nodered.org/t/catch-errors-during-flow-deployment/33096)._