# 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:** 6

<div class="post-metadata">

**Author:** ![mahe](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/mahe/32/19849_2.png) [@mahe](https://www.thethingsnetwork.org/forum/u/mahe)\
**Post date:** [September 15, 2017, 1:29pm UTC](https://www.thethingsnetwork.org/forum/t/my-applications-downlink-is-always-queued-for-next-uplink/7014/6 "2017-09-15T13:29:00Z")

</div>

Hi!

I’m wondering if this is still the plan? I’m working on a project, where I would like to be able to send a downlink IF the uplink is something specific (scheduled e.g. by a HTTP request)… Is this considered possible? I read somewhere else, that if the downlink is received later than 100 ms from the uplink, it will be scheduled for the next transmission:

> [@Problems receiving downlinks using the Java API](https://www.thethingsnetwork.org/forum/t/problems-receiving-downlinks-using-the-java-api/5877/3):
>
> We do understand that some applications might require sending an immediate reply, so we allow for a short wait time of 100ms. If your application takes 500ms to respond, the downlink will have missed this window, and will be scheduled for the next opportunity.

Is this still the case?

I am quite new to a lot of this, so I don’t know if that makes it impossible to schedule a downlink for an incoming uplink?

Thanks!

---

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