Closed beckyconning closed 2 years ago
The last request never reached our backend, which likely points to a network issue between the API gateway and the backend, given the fact that 504 is coming from the API gateway.
We will attempt to pinpoint the root case by working together with the API gateway team. In the meantime I would recommend that you implement a re-try strategy on your end, since the issue is intermittent and thus retrying should take care of it.
I will post back once I learn more.
Thank you!
Hi, we routinely get these errors however as you mention they are transient and so the auto retry strategy we've put in place to deal with them seems to resolve this. As such I'm going to close this issue.
I'm experiencing this reliably at one request often between 1052M and 1613M into the events dataset.
I could be wrong but my suspicion is that the API is just overstepping the timeout and that it occurs at this point in the dataset due to luck (the more requests in the load the more likely this is to happen).
Perhaps we can double the gateway timeout?
Thanks!
Second to last request:
Last request: