Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delta CalenderView API generalException error with the message "Unexpected exception returned from the service" #2169

Closed
raedaltaki opened this issue Oct 18, 2023 · 5 comments

Comments

@raedaltaki
Copy link

Many users are getting the generalException error with the message "Unexpected exception returned from the service" and HTTP status "ServiceUnavailable" when doing the delta CalenderView API request. then after a few days, the error resolves itself for these users and it starts throwing for different users.

To Reproduce
Steps to reproduce the behavior:
Unable to reproduce it. It just throws randomly and it solves itself after a few days

Expected behavior
the delta calenderView API request works for all users

Screenshots
image

Additional context
Add any other context about the problem here.

@andrueastman
Copy link
Member

Thanks for raising this @raedaltaki

The 503 response is a transient error that may be returned by the API in some situations and should be handled according to the guidance here.

From the feature flags in your trace it looks like the client has not enabled the RetryHandler that is used by the SDK to handle 503 responses from the API. Any chance you can confirm how you are initializing the client when making requests or do you have a custom retry mechanism?

@raedaltaki
Copy link
Author

We have a custom retry mechanism that handles this error by doing 3 retries when the "Service unavailable error" is thrown and waiting 5 seconds between retries. This didn't fix the issue.

Also, we tried adding the retry-after header to the API call and still have the same error.

This error happens randomly to different users and it fixes itself after some time (it can last for days)

@andrueastman
Copy link
Member

@raedaltaki Any chance you can try adding the retry-handler from the SDK to your middleware pipeline to see if there is any difference in the resilience here?

As this also sounds to be an API side issue due to service availability, any chance you can also follow up with support to create a service request to confirm if the API issue can be followed up?

https://developer.microsoft.com/en-us/graph/support

@raedaltaki
Copy link
Author

@andrueastman, I've opened a technical support ticket for this issue as you mentioned it sounds to be an API issue.

Also, I tried to add the retry-after in the header of the API requests but it didn't help.

@andrueastman
Copy link
Member

Thanks for this @raedaltaki. We'll close this for now.

Feel free to re-open/create a new issue in the event anything SDK related arises.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants