(Not a bug) API returned 500, help needed to debug. #2757
-
This is not a bug with the client, per se. Hence the reason I have not raised a bug report. I keep getting an internal server error with the API:
I don't have any access to my 100 Gb stored in OneDrive, not even the Web UI is working. Can't create documents, can't see what files I have through the Web UI - it's just all gone for now. Here's what the Web UI looks like, for reference: This is how all of this happened:
Yeah, I am sort of in the dark when it comes to debugging this. I've waited about 4 hours, and the issue still persists. Is there any specific OneDrive API support channel where I can get talking with actual people to resolve the issue? Also, I will say this. I know that OneDrive's API and the servers having some internal error (status 500) have nothing to do with this client, but I currently have no reason to believe that usage of the client was not what caused the issue. This was the first time that I attempted a large scale download of my OneDrive files with this client, I have previously only used |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
I was reading your response here, and saw that you talked about needing a full debug log in reference to an API status code 502. I know mine is actually 500, but anyways, here's as full log.
Not that promising tbh |
Beta Was this translation helpful? Give feedback.
-
Well this is alleviating. Seems there's currently an outage. Users are reporting things here too. It seems that I was a victim of bad timing with the outage and me performing a large-scale sync. |
Beta Was this translation helpful? Give feedback.
-
@kalyanoliveira As you know, any 5xx error message - regardless is a Server Side Issue and not a client side problem. |
Beta Was this translation helpful? Give feedback.
@kalyanoliveira
This page is always your friend when any client is generating 5xx errors: https://portal.office.com/servicestatus
As you know, any 5xx error message - regardless is a Server Side Issue and not a client side problem.