# Getting context deadline exceeded error when using REST API login every hour **URL:** \ **Category:** General Discussions\ **Created:** [October 1, 2020, 6:22am UTC](https://hub.mender.io/t/getting-context-deadline-exceeded-error-when-using-rest-api-login-every-hour/2605 "2020-10-01T06:22:25Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [October 1, 2020, 6:22am UTC](https://hub.mender.io/t/getting-context-deadline-exceeded-error-when-using-rest-api-login-every-hour/2605/1 "2020-10-01T06:22:25Z")
Hi I have test app which every hour login to mender server and perform some actions. From time to time I see that login fails with error: ```auto context deadline exceeded ``` Any advice how to resolve this? Is polling every hour too much? Server version 2.1.0 Thanks. Marek ---
**Author:** ![MarekBelisko](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/marekbelisko/32/33_2.png) [@MarekBelisko](https://hub.mender.io/u/MarekBelisko)\ **Post date:** [October 1, 2020, 1:05pm UTC](https://hub.mender.io/t/getting-context-deadline-exceeded-error-when-using-rest-api-login-every-hour/2605/2 "2020-10-01T13:05:48Z")
Also one more thing which is REST API related: [https://docs.mender.io/api/#tocs\_device-authentication-responseheaders](https://docs.mender.io/api/#tocs_device-authentication-responseheaders) shouldn’t return also total-number of devices so pagination can be then done easily (similar to: [https://docs.mender.io/api/#tocs\_device-inventory-responseheaders](https://docs.mender.io/api/#tocs_device-inventory-responseheaders)) Thanks. ---
**Author:** ![drewmoseley](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/drewmoseley/32/47_2.png) [@drewmoseley](https://hub.mender.io/u/drewmoseley)\ **Post date:** [October 1, 2020, 5:52pm UTC](https://hub.mender.io/t/getting-context-deadline-exceeded-error-when-using-rest-api-login-every-hour/2605/3 "2020-10-01T17:52:55Z")
@0lmi do you have anything to add here? I suspect the context deadline is related to rate limiting. ---
**Author:** ![0lmi](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/0lmi/32/133_2.png) [@0lmi](https://hub.mender.io/u/0lmi)\ **Post date:** [October 2, 2020, 12:16pm UTC](https://hub.mender.io/t/getting-context-deadline-exceeded-error-when-using-rest-api-login-every-hour/2605/4 "2020-10-02T12:16:27Z")
@MarekBelisko It doesn’t look like application response error and most likely this means that the scrape request timed out. Might be some network related issues or server slowness. If nothing in api-gateway logs than that is what I would check first. Also might be an option to try to increase scrape timeout in your test app. ---
**Author:** ![tranchitella](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tranchitella/32/606_2.png) [@tranchitella](https://hub.mender.io/u/tranchitella)\ **Post date:** [October 2, 2020, 12:18pm UTC](https://hub.mender.io/t/getting-context-deadline-exceeded-error-when-using-rest-api-login-every-hour/2605/5 "2020-10-02T12:18:37Z")
Hello @MarekBelisko, `context deadline exceeded` means that the request timed out. This usually happens if hit the nginx (api gateway) timeout, which defaults to 60 seconds. It is quite strange it happens when you log in, though, because it is unlikely it can take so long to get back the response. Do you know the response time, when you get back this error message? Is your mongodb always reachable, and does DNS resolution work fine from the Mender server containers? ---
**Author:** ![tranchitella](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/tranchitella/32/606_2.png) [@tranchitella](https://hub.mender.io/u/tranchitella)\ **Post date:** [October 2, 2020, 12:19pm UTC](https://hub.mender.io/t/getting-context-deadline-exceeded-error-when-using-rest-api-login-every-hour/2605/6 "2020-10-02T12:19:40Z")
@drewmoseley rate limiting would reply back with `429 Too Many Requests`