# How reliable are downlinks?

**URL:** <https://www.thethingsnetwork.org/forum/t/how-reliable-are-downlinks/37737>\
**Category:** LoRaWAN Discussions\
**Created:** [June 12, 2020, 6:19am UTC](https://www.thethingsnetwork.org/forum/t/how-reliable-are-downlinks/37737 "2020-06-12T06:19:20Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [June 13, 2020, 10:13am UTC](https://www.thethingsnetwork.org/forum/t/how-reliable-are-downlinks/37737/9 "2020-06-13T10:13:19Z")

</div>

> [@arjanvanb](#):
>
> As for _confirmed_ downlinks, you may also want to check what happens if you replace it while it was not yet confirmed.

Ah, the following was actually confirmed to work:

> [@TTGO Beam: Bootloop after config (Paxcounter)](https://www.thethingsnetwork.org/forum/t/ttgo-beam-bootloop-after-config-paxcounter/33384/2):
>
> You scheduled a _confirmed_ downlink. And apparently TTN is not getting a confirmation from your node, so rightfully repeats the downlink.
> 
> I _think_ you could schedule another downlink, ensuring it’s not set to be confirmed, and ensuring it has “Scheduling” set to “replace”, to discard the current confirmed downlink.

So, I’m quite sure confirmed downlinks can be replaced with a different confirmed downlink just fine.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/how-reliable-are-downlinks/37737)._