# MAC commands being sent each time after Join Process

**URL:** <https://www.thethingsnetwork.org/forum/t/mac-commands-being-sent-each-time-after-join-process/55569>\
**Category:** LMIC\
**Created:** [March 2, 2022, 11:18am UTC](https://www.thethingsnetwork.org/forum/t/mac-commands-being-sent-each-time-after-join-process/55569 "2022-03-02T11:18:06Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [March 2, 2022, 11:37am UTC](https://www.thethingsnetwork.org/forum/t/mac-commands-being-sent-each-time-after-join-process/55569/4 "2022-03-02T11:37:08Z")

</div>

> [@DylanWork](#):
>
> I am starting to see more devices perform this extra step, which adds somewhere around 10 seconds of waiting for my device at a time when our users are likely to be impatient, 10 extra seconds is a long time when your in a rush.

How does the downlink add an extra 10 seconds time and given that the expected metric for overall packet loss is 10%, what on earth is this device doing that people are in a rush?

There is another thread discussing [this](https://www.thethingsnetwork.org/forum/t/ttn-mapper-data-present-but-heatmap-is-not-shown/55436) and I am performing tests with additional logging to investigate.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/mac-commands-being-sent-each-time-after-join-process/55569)._