# How to purge a scheduled confirmed downlink

**URL:** <https://www.thethingsnetwork.org/forum/t/how-to-purge-a-scheduled-confirmed-downlink/56849>\
**Category:** The Things Stack v3\
**Created:** [May 4, 2022, 11:42am UTC](https://www.thethingsnetwork.org/forum/t/how-to-purge-a-scheduled-confirmed-downlink/56849 "2022-05-04T11:42:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![descartes](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/descartes/32/47220_2.png) [@descartes](https://www.thethingsnetwork.org/forum/u/descartes)\
**Post date:** [May 4, 2022, 11:52am UTC](https://www.thethingsnetwork.org/forum/t/how-to-purge-a-scheduled-confirmed-downlink/56849/2 "2022-05-04T11:52:14Z")

</div>

Did you try the options in my post which you ❤ ??

> [@How to clear downlink queue programmatically?](https://www.thethingsnetwork.org/forum/t/how-to-clear-downlink-queue-programmatically/49212/6):
>
> Yes, general problem with sequencing, no, there is no general solution, it’s very much situational. Whilst we now have a potential 3 or so seconds to process an uplink and queue a response, this is ambitious and as we need to code for up or downlinks not arriving as expected, prone to some interesting failure modes. This possibly indicates you are thinking of downlinks as a thing. Downlinks should be treated as an exception. Everything and anything - but again, it sounds like a scheme pre…

It also refers to your last statement - I’d find it odd if I typed a command to get a list of devices and got back a list of downlinks.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/how-to-purge-a-scheduled-confirmed-downlink/56849)._
