I'm constantly getting repeated 504 - Gateway Timeout (after 15 seconds) when trying to access activation reports via Microsoft Graph.
Occasionally, the query succeeds, but often after 11-12 seconds.
The subsequent CSV data download can take close to a minute to download 401 bytes!
Something is clearly not working as it should:
Related
When an API call is made after receiving an SMS via Twilio, I occasionally get the error below -
Error: Total timeout is triggered. Configured tt is 15000ms and we attempted 1 time(s)
The API call occasionally takes longer than 15 seconds to return a response (this is due to having to process the SMS etc.). How can I configure the total timeout to say 25000ms?
It is possible to override the timeout settings for a webhook. However, the maximum total time (tt) for webhooks is 15 seconds and you cannot increase it beyond there.
If you find your service cannot respond within that time, you might want to hand off the processing of the SMS to a job and respond to the webhook quicker. If you then intend to reply to the SMS, you can do so using the REST API message resource instead of TwiML.
we are using Microsoft Graph notification to monitor certain resource changes such as group creation/deletion, etc.
In the MS doc it says "Send a 202 - Accepted status code in your response to Microsoft Graph. If Microsoft Graph doesn't receive a 2xx class code, it will retry the notification a number of times."
We'd want to have a better understanding on how this works, such as what are the timeout values (how long does Graph wait before it re-sends the notification?), and how many times it retries (is it a guaranteed delivery?), etc. Can anybody help shed some light on this?
I was writing a script to create and fill playlists on my channel yesterday ( using playlist.insert and playlistItems.insert) when i received a 403 response with this message:
"The request cannot be completed because you have exceeded your
\u003ca
href=\"/youtube/v3/getting-started#quota\"\u003equota\u003c/a\u003e"
I think this is really strange because when i check my quota at https://console.developers.google.com/apis/api/youtube.googleapis.com/quotas i'm way below my daily quota with only 32.554 queries (1 million is the daily limit). I decided to wait until midnight PST for my quota to reset but i still can't make requests.
Is there anything i can do to reset my quota?
I am developing an iOS app that makes an API request to my server hosted in Heroku.
In my slow internet connection environment, the API request (via Http Get) sometimes results in a timeout. The response time is usually 2000 ms if not timing out.
By "sometimes", I mean about one in 10 requests times out (I do not get any meaningful error code).
I also tested this timeout with 2 devices. When one device is waiting for the server to respond for longer than 2000 ms, I use another device to call the api, to which the server responds normally. But the first device still results in a timeout.
I am not quite sure what is to blame here. My internet connection? My api server on Heroku? I also tested this timeout on Postman and got the same results.
PS. I am based out of Bangkok. The ISP with which I experience the most timeouts is True Broadband.
Any and all advice is appreciated.
Thanks in advance
PPS. In response to comments warning that the question is too broad: Let's ask it this way. If our api calls randomly time out, how can we detect whether it is due to a slow internet connection, or if the fault lies in our own server (or something else)?
My application is communicating with a service. The service provides user login , registration , update functionality (IAM Service) . Since, this feature is critical & we don't want to impact user performance, we set the timeout 500 millisec, considering the fact that both my application & the IAM service are in the same data center.
On analysis, we found that the IAM service on an average takes 10 - 12 millisecs & my application which simply sends the request takes 1 - 2 millisecs. Also, it does not happen for every request, just a few request.
The network engineer says the network is good & there are no leaks.
Request your inputs to understand, how should I proceed to analyze the root cause to recognize which component is taking time.
Make sure the Application and the Service are synchronized (have the same time stamp)
Log the Time stamp of request being sent by the App
Observe the time stamp when the request hits the wire
Log the Time stamp when the Request is being received by the Service
Log the time stamp when the Service sends out the response
Observe the time stamp when the response hits the wire
Log the time stamp when the app receives the response
The next time the timeout occurs - check the log to find out which two laterally adjacent time stamps have a difference of more than the 500ms. Now once you have the profiled information - focus on the particular segment that causes the timeout.