# Critical ! Message is discarded when MQTT out node is in Connection state

**URL:** <https://discourse.nodered.org/t/critical-message-is-discarded-when-mqtt-out-node-is-in-connection-state/78539>\
**Category:** General\
**Created:** [19 May 2023 11:09 UTC](https://discourse.nodered.org/t/critical-message-is-discarded-when-mqtt-out-node-is-in-connection-state/78539 "2023-05-19T11:09:28Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [19 May 2023 11:35 UTC](https://discourse.nodered.org/t/critical-message-is-discarded-when-mqtt-out-node-is-in-connection-state/78539/4 "2023-05-19T11:35:29Z")

</div>

You could queue the messages with the delay node and rate limit, set to a high rate delay. Then use a status node to start flushing the messages, once connected and queue again if disconnected. read the help text on these nodes to see how this would work, there are also many examples of this on the forum, This [post](https://discourse.nodered.org/t/announce-improved-guaranteed-delivery-flow/39877) may help to

---

_[View the full topic](https://discourse.nodered.org/t/critical-message-is-discarded-when-mqtt-out-node-is-in-connection-state/78539)._