Graph API/SDK Bad Gateway 502

Jon Tereba 1 Reputation point

We use the Graph API to hit SharePoint Libraries and Lists and occasionally run into BadGateway (502) response codes from the Graph Client SDK and API. I believe that the SDK is supposed to retry if the status code is ServiceUnavailable, GatewayTimeout, or 429. This is returning a BadGateway though. If I attempt to retry, eventually it goes through. This 502 response seems to happen if the request takes longer than 40 seconds to respond. I'm looking for information on what causes this issue and any solutions that can implement to avoid this in the future. There was a period of 12 hours several weeks ago where all we got were 502 responses for any Drives or Sites Graph requests.

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
35,795 questions
{count} votes