503 Error coming up from Microsoft Graph API

Question

503 Error coming up from Microsoft Graph API

Usman Ahmad 0

I am getting http status code 503 on a request to graph API. The request I am making is as follows:

https://graph.microsoft.com/beta/deviceManagement/managedDevices/device-id?$select=physicalMemoryInBytes,ethernetMacAddress,userId,usersLoggedOn,hardwareInformation&$expand=detectedApps

Here device-id was replaced by the device id of the device. The response I am getting is the follows:


"error": {
        "code": "DQCancelledOnRequestTimeout",
        "innerError": {
          "client-request-id": "2d6f7c74-0648-41b7-bc14-3d05bb7833f3",
          "date": "2023-03-02T20:02:27",
          "request-id": "2d6f7c74-0648-41b7-bc14-3d05bb7833f3"
        },
        "message": "{\r\n  \"_version\": 3,\r\n  \"Message\": \"An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: 2d6f7c74-0648-41b7-bc14-3d05bb7833f3 - Url: https://fef.msub02.manage.microsoft.com/DeviceFE/StatelessDeviceFEService/deviceManagement/managedDevices('<device-id>')?api-version=5022-11-15&$select=physicalMemoryInBytes%2cethernetMacAddress%2cuserId%2cusersLoggedOn%2chardwareInformation&$expand=detectedApps\",\r\n  \"CustomApiErrorPhrase\": \"\",\r\n  \"RetryAfter\": null,\r\n  \"ErrorSourceService\": \"\",\r\n  \"HttpHeaders\": \"{}\"\r\n}"
      }

Here device id is replace by <device-id>.

I have read the documentation and it says to wait some time specified by the Retry-After header and then try sending the request again, but in this case the RetryAfter seems to be null (from the message above).

1 answer

Your answer

Answer 1

Crystal-MSFT 53,981 Microsoft External Staff

@Usman Ahmad, Thanks for posting in Q&A.

Based on my test, we can use the following format to get the managed device information:

https://graph.microsoft.com/beta/deviceManagement/manageddevices('<device id>')?$select=physicalMemoryInBytes,ethernetMacAddress,userId,usersLoggedOn,hardwareInformation&$expand=detectedApps

User's image

Hope it can help.

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

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Usman Ahmad 0 Reputation points

2023-03-06T11:42:04.71+00:00

Hi Crystal,

Thank you for answering.

My problem is not that I am unable to get devices information by hitting the API url, but it is getting the correct response back consistently. Most of the times I hit this API I am getting the devices but sometimes I am getting 503 and 504 errors (error response given in original question). Now the documention on errors does suggest to wait an amount of seconds given in 'Retry-After' header. But as we can see in the error response (given in original question) the 'RetryAfter' is coming up as null, so what am I supposed to do in this case ?
Usman Ahmad 0 Reputation points

2023-03-06T11:42:05.57+00:00

Hi Crystal,

Thank you for answering.

My problem is not that I am unable to get devices information by hitting the API url, but it is getting the correct response back consistently. Most of the times I hit this API I am getting the devices but sometimes I am getting 503 and 504 errors (error response given in original question). Now the documention on errors does suggest to wait an amount of seconds given in 'Retry-After' header. But as we can see in the error response (given in original question) the 'RetryAfter' is coming up as null, so what am I supposed to do in this case ?
Crystal-MSFT 53,981 Reputation points Microsoft External Staff

2023-03-07T01:42:59.67+00:00

@Usman Ahmad, Thanks for the reply. From the error code, it seems the time you get the issue is with the timeout issue. Maybe you can capture network logs on the devices and network devices to see if any request is dropped in the middle.
Usman Ahmad 0 Reputation points

2023-03-07T10:38:49.2+00:00

So this is not issue with timeout on our end. As I have pasted the response in the original post, this is the response coming up from a Microsoft server. Microsoft Graph API returns error responses in this format (response given in original post).
Usman Ahmad 0 Reputation points

2023-03-07T10:40:34.86+00:00

@Crystal-MSFT ^
Crystal-MSFT 53,981 Reputation points Microsoft External Staff

2023-03-08T06:18:30.2366667+00:00

@Usman Ahmad, Thanks for the reply. If the timeout comes from backend server, I think you need open a premier case to check on it. Here is a link with the steps to open case for the reference:

https://learn.microsoft.com/en-us/mem/get-support
Usman Ahmad 0 Reputation points

2023-03-08T06:35:14.95+00:00

Alright I will ask via customer support

Share via

503 Error coming up from Microsoft Graph API

1 answer

Your answer