# MQTT - Storing data when disconnected

**URL:** <https://discourse.nodered.org/t/mqtt-storing-data-when-disconnected/9306>\
**Category:** General\
**Created:** [22 March 2019 08:56 UTC](https://discourse.nodered.org/t/mqtt-storing-data-when-disconnected/9306 "2019-03-22T08:56:29Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![paul404](https://avatars.discourse-cdn.com/v4/letter/p/bc79bd/32.png) [@paul404](https://discourse.nodered.org/u/paul404)\
**Post date:** [23 March 2019 10:10 UTC](https://discourse.nodered.org/t/mqtt-storing-data-when-disconnected/9306/9 "2019-03-23T10:10:52Z")

</div>

So the Node-RED mqtt node has made qos 1 and 2 redundant by having a connection check around publish. The underlying mqtt client lib already manages messages correctly based on qos. In fact the mqtt client can be configured with a storage policy. The default policy is es6-map.

If Node-RED is running in a constrained environment where qos\>0 can not be supported. Then I would expect qos to be set to 0 in that environment.

---

_[View the full topic](https://discourse.nodered.org/t/mqtt-storing-data-when-disconnected/9306)._