# How is frame count (FCnt) desyncronisation managed? (1.0.4+)

**URL:** <https://www.thethingsnetwork.org/forum/t/how-is-frame-count-fcnt-desyncronisation-managed-1-0-4/71298>\
**Category:** The Things Stack v3\
**Created:** [May 6, 2025, 1:35am UTC](https://www.thethingsnetwork.org/forum/t/how-is-frame-count-fcnt-desyncronisation-managed-1-0-4/71298 "2025-05-06T01:35:51Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![ElectronicallyE](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/electronicallye/32/48501_2.png) [@ElectronicallyE](https://www.thethingsnetwork.org/forum/u/ElectronicallyE)\
**Post date:** [May 6, 2025, 12:28pm UTC](https://www.thethingsnetwork.org/forum/t/how-is-frame-count-fcnt-desyncronisation-managed-1-0-4/71298/13 "2025-05-06T12:28:26Z")

</div>

With sensor deployments as large as what you have described, there indeed needs to be confidence in the network, particularly when there are outages.

Surely there is a threshold which The Things Network considers “acceptable” for the frame counter being above that expected. By knowing this number, you could be able to determine how long an outage would need to be in order to require a rejoin.

I appreciate that experimenting may lead to an answer, but isn’t there a max frame count gap programmed into the configuration to replace the previously defined standard of 16384?

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/how-is-frame-count-fcnt-desyncronisation-managed-1-0-4/71298)._