# TTGO Beam: Bootloop after config (Paxcounter)

**URL:** <https://www.thethingsnetwork.org/forum/t/ttgo-beam-bootloop-after-config-paxcounter/33384>\
**Category:** End Devices (Nodes)\
**Created:** [January 14, 2020, 4:05pm UTC](https://www.thethingsnetwork.org/forum/t/ttgo-beam-bootloop-after-config-paxcounter/33384 "2020-01-14T16:05:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [January 14, 2020, 4:28pm UTC](https://www.thethingsnetwork.org/forum/t/ttgo-beam-bootloop-after-config-paxcounter/33384/2 "2020-01-14T16:28:11Z")

</div>

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.

![Schedule downlink](https://www.thethingsnetwork.org/forum/uploads/default/original/3X/1/f/1f3420b9dee3a0ecbe15a5d8b719536592fe1822.png)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/ttgo-beam-bootloop-after-config-paxcounter/33384)._