Hello everyone,
I wanted to provide an update regarding the GraphFatalServiceException
and ErrorInternalServerError
encountered when calling:
bash
Copy
GET https://graph.microsoft.com/v1.0/me/calendars
Status: Resolved
I have re-tested the API using Graph Explorer, and the request now returns a successful 200 OK
response along with full calendar details.
Key Observations:
All expected calendars (default, holiday, birthday, shared) were returned.
Fields such as canEdit
, canShare
, allowedOnlineMeetingProviders
, etc., were included as expected.
The operation executed successfully with no delay.
Possible Cause:
This was likely a transient issue on the Microsoft Graph backend service.
Another potential factor could be the way the SDK (graph-java/v4.0.0
) processes the response or handles temporary service failures.
Recommendations:
In production, consider using filtered queries (e.g., GET /me/calendars?$select=id,name
) to reduce payload size.
- Implement retry logic and exponential backoff for
5xx
errors to handle temporary server issues gracefully.Hello everyone, I wanted to provide an update regarding theGraphFatalServiceException
andErrorInternalServerError
encountered when calling:
Status: Resolved I have re-tested the API using Graph Explorer, and the request now returns a successfulbash Copy GET https://graph.microsoft.com/v1.0/me/calendars
200 OK
response along with full calendar details. Key Observations:- All expected calendars (default, holiday, birthday, shared) were returned.
- Fields such as
canEdit
,canShare
,allowedOnlineMeetingProviders
, etc., were included as expected. - The operation executed successfully with no delay.
- This was likely a transient issue on the Microsoft Graph backend service.
- Another potential factor could be the way the SDK (
graph-java/v4.0.0
) processes the response or handles temporary service failures.
- In production, consider using filtered queries (e.g.,
GET /me/calendars?$select=id,name
) to reduce payload size. - Implement retry logic and exponential backoff for
5xx
errors to handle temporary server issues gracefully.