# Node-red MQTT QOS does not work?

**URL:** <https://discourse.nodered.org/t/node-red-mqtt-qos-does-not-work/79819>\
**Category:** General\
**Created:** [14 July 2023 13:28 UTC](https://discourse.nodered.org/t/node-red-mqtt-qos-does-not-work/79819 "2023-07-14T13:28:48Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [18 July 2023 07:55 UTC](https://discourse.nodered.org/t/node-red-mqtt-qos-does-not-work/79819/8 "2023-07-18T07:55:01Z")

</div>

Sorry Steve, I only just noticed your reply.  
I'll have to do some more reading on mqtt 5, was not aware of session expiry vs keep alive.

I was looking at another thread [https://discourse.nodered.org/t/edge-to-cloud-computing/79815](https://discourse.nodered.org/t/edge-to-cloud-computing/79815) about making data transfer resilient over network drop-outs.  
I thought "Surely MQTT already does this?" but it seems not, except with the single most recent retained message (per topic). Hence this thread.

---

_[View the full topic](https://discourse.nodered.org/t/node-red-mqtt-qos-does-not-work/79819)._