# How to clear downlink queue programmatically?

**URL:** <https://www.thethingsnetwork.org/forum/t/how-to-clear-downlink-queue-programmatically/49212>\
**Category:** Application Development\
**Created:** [June 28, 2021, 10:56pm UTC](https://www.thethingsnetwork.org/forum/t/how-to-clear-downlink-queue-programmatically/49212 "2021-06-28T22:56:10Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![kersing](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/kersing/32/44777_2.png) [@kersing](https://www.thethingsnetwork.org/forum/u/kersing)\
**Post date:** [June 29, 2021, 9:01am UTC](https://www.thethingsnetwork.org/forum/t/how-to-clear-downlink-queue-programmatically/49212/4 "2021-06-29T09:01:04Z")

</div>

> [@acutetech](#):
>
> However, the device does not receive the message (say it is reset).

The network doesn’t know about the device not receiving the message. After the uplink the downlink will be sent regardless of the device state. Unless you are using ACKed downlinks which is a very bad idea by itself (search the forum if you want to know why) the network considers the downlink sent.  
For V3 this will ‘fail’ if the downlink arrives after the 5 second RX window. At that point it will be scheduled for another uplink.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/how-to-clear-downlink-queue-programmatically/49212)._
