Microsoft Graph API receiving 400 UnknownError when getting second page of delta query

Question

Microsoft Graph API receiving 400 UnknownError when getting second page of delta query

Theo Lukens 10

The Microsoft Graph API consistently returns 400 Bad Request with body "UnknownError" when querying for the second page of a paginated delta query.

I'm calling the GET /users/{id | user-principal-name}/chats/getAllMessages/delta endpoint documented here.

The initial request returns a @odata.nextLink URL which I then use in a subsequent request. This request works and I get another @odata.nextLink URL, but this one consistently fails with the error above.

Any help debugging this would be much appreciated!

1 answer

Your answer

Answer 1

Carolyne-3676 291

Hello Theo!
Thanks for reaching out.
This error suggests that there might be an issue with the request or the data being returned.
Here are a couple of troubleshooting steps:

Token Expiry: Ensure that the token you're using for the request hasn't expired. If it has, you'll need to obtain a new one.

Incorrect URL: There might be an error in the URL you're using for the second request. Ensure that the @odata.nextLink URL you received from the first request is being used correctly such that there are no modifications. URL encoding can sometimes cause problem hence copying and pasting the URL into a text editor that shows hidden characters can help identify any issue
Inspect the Request Headers: Verify that the request headers for the subsequent request are correctly set. Ensure that you are including any necessary headers such as Authorization.
Retry Logic: Implement retry logic with exponential backoff to handle transient issues.
Token Expiry: Ensure that the token you're using for the request hasn't expired. If it has, you'll need to obtain a new one.

Try and capture the logs and if this persists, please share the correlation ID and timestamp details for investigation.

Theo Lukens 10 Reputation points

2025-04-23T10:46:52.0533333+00:00
Thanks for the response. In answer to your points:

Incorrect URL: I've verified that the @odata.nextLink is valid and has no encoding errors or modifications. To be clear, the first @odata.nextLink I receive works fine, it's the second that fails.

Inspect the Request Headers: All headers, including Authorization are fine

Retry Logic: I implemented retry logic but this doesn't help

Token Expiry: I get a new access token every request, so this is not an issue

For additional information, I tried to compare the two @odata.nextLink URLs I received as one worked and one did not. As they are encoded it's difficult to compare anything other than the length, but the link that doesn't work is definitely longer than the working one.

Could I be hitting some internal msgraph length limit on nextLink URLs or skipTokens?
Carolyne-3676 291 Reputation points

2025-04-23T11:42:00.5066667+00:00

I see. Please share corelation ID and timestamp so we can take a look.
Theo Lukens 10 Reputation points

2025-04-23T11:47:20.3633333+00:00
Thanks. Here's the info (date is UTC):

{ "date":"2025-04-23T11:46:37", "client-request-id":"8c9f81a5-eb9d-4b54-86de-e9d3617380a2" }
Sumeet Dewangan 0 Reputation points

2025-04-27T23:51:14.3133333+00:00

Hi @Theo Lukens , was there any resolution for this issue?

I see the same issue when using delta API. All the parameters that Carolyne mentioned above looks fine to me - however still stuck on the same error.
Theo Lukens 10 Reputation points

2025-04-28T09:41:29.5733333+00:00

Hi @Sumeet Dewangan , I'm still waiting for a response from @Carolyne-3676 and the error still persists. Any progress there?
Carolyne-3676 291 Reputation points

2025-05-02T08:37:04.9566667+00:00

Apologies for the delayed response here- yes I did check the logs and there is no indication of any issue that could lead to this error. I am looking into ways to unblock and will revert on this thread. May I ask what version of the SDK you are using if you are using an SDK? Let me know.
Looking for a speedy resolution to this issue.
Theo Lukens 10 Reputation points

2025-05-02T09:24:27.8266667+00:00
Thanks Carolyne. I'm not using an SDK, just pure HTTP requests. The sequence of events is like this:

Make an initial request to /users/{id | user-principal-name}/chats/getAllMessages/delta

200 Success response and a batch of messages in the response body

Make a request to the @odata.nextLink URL in the response from request 1

200 Success response and another batch of messages in the response body

Make a request to the @odata.nextLink URL in the response from request 2

400 Bad Request response with UnknownError in the response body

The @odata.nextLink URLs in steps 2 and 3 always look very similar, except the $skiptoken query string in step 3 is always longer - could it be that some internal length limit is being his that causes this error?

Share via

Microsoft Graph API receiving 400 UnknownError when getting second page of delta query

1 answer

Your answer