# My application's downlink is always queued for next uplink

**URL:** <https://www.thethingsnetwork.org/forum/t/my-applications-downlink-is-always-queued-for-next-uplink/7014>\
**Category:** TTN Network and Services\
**Created:** [May 1, 2017, 9:33am UTC](https://www.thethingsnetwork.org/forum/t/my-applications-downlink-is-always-queued-for-next-uplink/7014 "2017-05-01T09:33:32Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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 12, 2018, 9:00am UTC](https://www.thethingsnetwork.org/forum/t/my-applications-downlink-is-always-queued-for-next-uplink/7014/7 "2018-01-12T09:00:13Z")

</div>

> [@htdvisser](#):
>
> If the application is not fast enough, the downlink is scheduled for the next opportunity.

And for future reference, this “next opportunity” refers to the next uplink (not to RX2 when the application is too late for RX1):

> [@Configure Downlink Frequency of a Gateway](https://www.thethingsnetwork.org/forum/t/configure-downlink-frequency-of-a-gateway/4038/21):
>
> The application has a fixed time to respond to uplink messages directly, regardless of the selected RX window. If the application is too slow for that, the response is scheduled for the next opportunity.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/my-applications-downlink-is-always-queued-for-next-uplink/7014)._