Lately, we often encounter this 504 Gateway timeout on multiple endpoints
Example of /preview endpoint:
Server error: `POST https://graph.microsoft.com/v1.0/sites/root/drive/items/014THVUXPVDHARRLTKGZHI2GLKYADOOZDI/preview` resulted in a `504 Gateway Timeout` response:
{
"error": {
"code": "UnknownError",
"message": "",
"innerError": {
"request-id": "3f981b5d-883 (truncated...)
another example on small file upload endpoint:
PUT /content?#microsoft.graph.conflictBehavior=rename` resulted in a `504 Gateway Timeout` response:
{
"error": {
"code": "UnknownError",
"message": "",
"innerError": {
"request-id": "12d80986-9cb (truncated...)
Please test the above API calls with Microsoft Graph Explorer and see if you can still repro the issue.
Related
When accessing data using https://graph.microsoft.com/beta/teams/{id}, it is failing with 400 bad request without any error details. {id} is the value received from the response of https://graph.microsoft.com/beta/groups.
Following response is returned.
{
"error": {
"code": "AuthenticationError",
"message": "Error authenticating with resource",
"innerError": {
"date": "2021-10-15T15:01:43",
"request-id": "1d82fe40-5186-46fc-9fb7-c16341eb1ffb",
"client-request-id": "29c9e68d-bfd8-6f53-65c4-c49a82581a76"
}
}
}
We tried using MS graph SDK as well as graph explorer. All the consent are given for the end point.
What could be the reason for the error?
Getting below error while running labels available to the organization after providing the required permission
https://graph.microsoft.com/beta/informationProtection/policy/labels
{
"error": {
"code": "UnknownError",
"message": "502 Bad Gateway",
"innerError": {
"date": "2020-11-24T07:12:06",
"request-id": "3fa2b70d-79fd-4ade-b16d-1250be2771a1",
"client-request-id": "02b1ac97-21c6-75c4-0cbb-403ab53a1108"
}
}
}
HTTP 502 tells that the API call service is unavailable at the time, when you tried calling. I would suggest you to test the same after sometime to see if it works. If you still see the issue, you can report the issue back here. Also i see that its under beta endpoint, which is not meant for production environments
I need to read the list of synchtonizationProfile entities. I get accessToken using grant_type=code and requested permissions for EduAdministration.Read and EduAdministration.ReadWrite (as specified in the documentation).
But when I try the request, I get the following error:
{
"error": {
"code": "AuthenticationError",
"message": "Error authenticating with resource.",
"innerError": {
"request-id": "1a47270e-f902-48af-81cc-5ed8e279b050",
"date": "2017-12-21T12:20:27"
}
}
}
The problem only with the /synchronizationProfiles endpoint.
What is the problem? And how to solve it?
Hello I am getting several skip token errors when running a full import on the graph API.
here is the error
The following one looks like expiration of skiptoken. Graph connector uses skip token in different cases. I would communicate with Graph API team to understand if this is correct behavior for the API.
Message: Error during http call. HttpStatusCode: BadRequest;
url: https://graph.microsoft.com:443/v1.0/groups/5802115b-ef14-4572-bec1-9a4747e5bcfb/members/?$select=id&$skiptoken=X%2744537074090001000000000000000010000000D6203A9D758C6F4B887B307BA3302EB5000000000000000000000017312E322E3834302E3131333535362E312E342E323333310000000000000157F232736047814E848C20B3547FF5E8%27;
Response: {
"error": {
"code": "Directory_ExpiredPageToken",
"message": "The specified page token value has expired and can no longer be included in your request.",
"innerError": {
"request-id": "1489b123-f94c-4531-82d1-d4b76331e3eb",
"date": "2017-11-27T18:59:23"
}
}
}
Message: Error during http call. HttpStatusCode: Unauthorized;
"code": "Authentication_MissingOrMalformed",
"message": "Access Token missing or malformed.",
The application has full control over all objects so it should not get an error with permissions issues
POST https://graph.microsoft.com/v1.0/me/messages/AAMkADFkZDdjMWM0LTg2MzYtNGI4ZC1hNDAzLWY2NDljZmZmZDM4YQBGAAAAAAAy50dDcjLxRroxR16zN80WBwAqP1cdrk5dTLdAWYlr7M8QAAAAAAEPAAAqP1cdrk5dTLdAWYlr7M8QAAChu4WSAAA=/send
Suddenly started throwing this now (first it was seen on the beta endpoints. Now it is coming on v1.0 as well
{
"error": {
"code": "InternalServerError",
"message": "Object reference not set to an instance of an object.",
"innerError": {
"request-id": "eecf9817-1c44-4fa5-aabb-f975f8496484",
"date": "2016-09-25T09:16:43"
}
}
}