lasator | 2016-09-14 23:16:20 UTC | #1
Hello,
I'm currently working on a desktop integration with PureCloud using the REST api. I've noticed that occasionally I receive a Gateway Timeout from a request. It is infrequent but can cause significant issues with the integration. Is there a standard way to handle this situation? When the timeout does occur, there is a pause of around 10 seconds before the error is returned.
KevinGlinski | 2016-09-14 16:16:44 UTC | #2
are there specific resources that timeout? is there any response body for the timeouts?
lasator | 2016-09-14 20:14:43 UTC | #3
It doesn't appear that there is any response content. It's a 504 Gateway Timeout response. I see this most frequently when attempting to put the list of notification topics or retrieving the agent's current status directly.
lasator | 2016-09-14 20:26:09 UTC | #4
I was just able to reproduce this with Postman and it has some more information: Cache-Control →no-cache, no-store, must-revalidate Connection →keep-alive Content-Length →74 Content-Type →application/json Date →Wed, 14 Sep 2016 20:24:47 GMT Expires →0 ININ-Correlation-Id →00176362-6bee-4744-8150-49f14ec91f8f Pragma →no-cache Via →1.1 5ead76a58ac4f48d1b89fffd1e73667c.cloudfront.net (CloudFront) X-Amz-Cf-Id →RpaJGIEzadLpYTLlNqKJC3tGQI2E6IkxaQAiGEz2yH9-zpca2YRvzQ== X-Cache →Error from cloudfront inin-ratelimit-allowed →300 inin-ratelimit-count →5 inin-ratelimit-reset →57
system | 2017-08-28 19:27:16 UTC | #5
This post was migrated from the old Developer Forum.
ref: 400