503 "Service Unavailable" for calendarView

Frank Cort 11 Reputation points
2022-10-26T21:22:58.947+00:00

Hi, We are running into a 503 "Service Unavailable" issue when fetching /calendarView/delta

Here is the request info:

url=https://graph.microsoft.com/v1.0/me/calendars/OMITTED/calendarView/delta?startDateTime=2022-09-26T21:19:48Z&endDateTime=2022-12-25T22:19:48Z
request-id=c97f5c6c-e475-424f-85f6-91c2a8e840b8
date=Wed, 26 Oct 2022 21:20:11 GMT
x-ms-ags-diagnostics={"ServerInfo":{"DataCenter":"South Central US","Slice":"E","Ring":"5","ScaleUnit":"005","RoleInstance":"SN4PEPF000006F0"}}

Please advise!

Microsoft Graph
Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
10,573 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Robin Bailleul 6 Reputation points
    2022-11-07T09:11:05.563+00:00

    We are experiencing the same behaviour, since October 27th approximately.
    Continually getting 503 responses when calling /calendarView/delta endpoint.
    For small periodes of less than a month (between startDateTime & endDateTime), the request succeeds.
    Larger periodes (a year, or - what we are interested in to use - several years) have consistently been failing with 503 for the last 10 days or so...
    The timing of this service being unavailable in the last weeks before the REST API is being deprecated, is very inconvenient, to say the least...

    1 person found this answer helpful.
    0 comments
  2. HarmeetSingh7172 4,811 Reputation points
    2022-10-27T01:24:06.907+00:00

    Hello @Frank Cort

    Thanks for reaching out!

    Error 503 comes when 'The service is temporarily unavailable for maintenance or is overloaded. You may repeat the request after a delay, the length of which may be specified in a Retry-After header'. Refer this documentation. You can retry the requests or increasing the timeout (Incase you are using any custom application increase the timeout for at least 2 min).

    Another reason could be likely because the services are busy. You should employ a back-off strategy similar to 429. Additionally, you should always make new retry requests over a new HTTP connection. Refer this documentation.

    Hope this helps!

    If the answer is helpful, please click Accept Answer and kindly upvote. If you have any further questions about this answer, please click Comment.

  3. Richard Mao 1 Reputation point
    2022-11-30T00:25:16.24+00:00

    We are also experiencing the same behaviour. We call /calendarView/delta and page over the results using the "@odata.nextLink". Many pages work fine, but eventually, we encounter the same 503 error as described above. Contrary to the suggestion that this is just some sort of temporary service outage, it never works regardless of the number of retries.

    We can re-issue the same delta request from the start and those will work and we can page over the results again, and they always work until the same page where we get the 503 error.

    It's also worth noting that we can also reproduce the problem with the /events/delta api (which is only available on the beta endpoint currently).

    We have a case open with Microsoft support as well. Hopefully they will be able to provide some answers.

    0 comments