Catch errors during flow deployment

[drmibell]

A similar issue 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.