Open calebdoxsey opened 1 year ago
We already implemented retries when access tokens expire.
Confirmed:
<nil> DBG http-request authority=graph.microsoft.com duration=129.826292 idp=azure method=GET path=/v1.0/users/delta response-body="{\"error\":{\"code\":\"InvalidAuthenticationToken\",\"message\":\"Access token has expired or is not yet valid.\",\"innerError\":{\"date\":\"2023-03-29T03:35:13\",\"request-id\":\"e5192c2d-960b-48ea-bc21-979ae759f671\",\"client-request-id\":\"e5192c2d-960b-48ea-bc21-979ae759f671\"}}}" response-code=401
<nil> DBG http-request authority=login.microsoftonline.com duration=430.282791 idp=azure method=POST path=/a0860b16-674e-426d-9165-f87469a8282d/oauth2/v2.0/token response-code=200
The token expires, we clear it and retry the next request, which succeeds.
What happened?
Occasionally when doing large sync calls with the Azure Microsoft Graph Delta API we are seeing timeouts:
What did you expect to happen?
For large directory syncs to succeed.
Additional context
We should investigate a few different ideas here:
$skiptoken
?Locally we should be able to reproduce the behavior by adding an artifical lag to all requests. The default access token expiration is between 60 and 90 minutes.