Issue with Pagination for Channel Message Replies using Microsoft Graph API ($skipToken returning empty results)

Question

Issue with Pagination for Channel Message Replies using Microsoft Graph API ($skipToken returning empty results)

Soumya Ranjan Mohanty 5

Hi Team,

I am facing an issue while retrieving replies to a channel message using Microsoft Graph API.

1. List replies API

GET /teams/{team-id}/channels/{channel-id}/messages/{message-id}/replies?$top=50

This API always returns a maximum of 50 replies (expected due to $top=50).
However, when I use the @odata.nextLink (which contains $skipToken) to fetch the next set of replies, the response is always an empty array ([]).

2. List channel messages with expanded replies

GET /teams/{team-id}/channels/{channel-id}/messages?$expand=replies

This returns up to 200 replies.
But when I use the replies@odata.nextLink value (exactly as returned) to paginate further, it again returns an empty array ([]).

Issue Summary

Pagination using $skipToken / @odata.nextLink is not returning subsequent pages.
The nextLink is used exactly as provided in the response.
This behaviour is consistent across both APIs.

Moderator's note: Moved from Microsoft Security | Microsoft Graph

Prasad-MSFT 10,491 Reputation points Microsoft External Staff Moderator

2026-05-12T05:04:57.13+00:00

Hi Soumya Ranjan Mohanty thank you for reporting the issue. We will investigate it on our end and keep you updated with our findings.
Giles Holmes 5 Reputation points

2026-05-12T20:48:07.3966667+00:00

I can also confirm this is now breaking in our production environment for the last two days. It is currently impossible to pull all of the messages in a channel. This is especially dangerous since there is no indication of an error. The nextLink just points to a result with an empty value.
Dora-T 13,825 Reputation points Microsoft External Staff Moderator

2026-05-13T04:09:12.25+00:00

Hi Giles Holmes

Thank you for sharing these additional observations.

The detail that this behavior started only within the last couple of days and is also affecting your production environment is helpful information for understanding the scope of the issue.

I also understand your concern regarding the lack of any explicit error response, since the nextLink request returning an empty value array could make the issue difficult to detect during normal pagination handling.

At this point, please wait for additional input from the MSFT team regarding the current behavior.

Thank you for your patience and understanding.
Prasad-MSFT 10,491 Reputation points Microsoft External Staff Moderator

2026-05-20T11:49:04.79+00:00

Hi Soumya Ranjan Mohanty, Giles Holmes we have raised an ICM for this issue and engineering team is looking into it. We will inform you once we have further update. Thanks!

1 answer

Your answer

Prasad-MSFT 10,491 Reputation points Microsoft External Staff Moderator

2026-05-12T05:04:57.13+00:00

Hi Soumya Ranjan Mohanty thank you for reporting the issue. We will investigate it on our end and keep you updated with our findings.
Giles Holmes 5 Reputation points

2026-05-12T20:48:07.3966667+00:00

I can also confirm this is now breaking in our production environment for the last two days. It is currently impossible to pull all of the messages in a channel. This is especially dangerous since there is no indication of an error. The nextLink just points to a result with an empty value.
Dora-T 13,825 Reputation points Microsoft External Staff Moderator

2026-05-13T04:09:12.25+00:00

Hi Giles Holmes

Thank you for sharing these additional observations.

The detail that this behavior started only within the last couple of days and is also affecting your production environment is helpful information for understanding the scope of the issue.

I also understand your concern regarding the lack of any explicit error response, since the nextLink request returning an empty value array could make the issue difficult to detect during normal pagination handling.

At this point, please wait for additional input from the MSFT team regarding the current behavior.

Thank you for your patience and understanding.
Prasad-MSFT 10,491 Reputation points Microsoft External Staff Moderator

2026-05-20T11:49:04.79+00:00

Hi Soumya Ranjan Mohanty, Giles Holmes we have raised an ICM for this issue and engineering team is looking into it. We will inform you once we have further update. Thanks!

Answer 1

Dora-T 13,825 Microsoft External Staff Moderator

Hi Soumya Ranjan Mohanty

I've tried reproducing your issue using both Postman and Microsoft Graph Explorer.

For the following endpoint:

GET /teams/{team-id}/channels/{channel-id}/messages/{message-id}/replies?$top=50

pagination worked as expected in my testing, and I was able to retrieve additional pages using the @odata.nextLink value returned by the API.

However, when testing:

GET /teams/{team-id}/channels/{channel-id}/messages?$expand=replies

the behavior was different.

On my side, the expanded replies stopped at 200 items and the response did not include replies@odata.nextLink, even though Microsoft documentation indicates that a continuation link should be returned when additional replies exist. So, at this time, the actual service behavior does not appear fully consistent with the documented behavior.

As forum moderators, we can help validate and compare the current behavior based on testing and publicly available Microsoft resources, but we do not have visibility into backend service implementation details.

In this case, please continue waiting for further investigation or clarification from the MSFT team (@Prasad-MSFT) regarding the pagination behavior for expanded replies.

Thank you for your patience and understanding.

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.

Soumya Ranjan Mohanty 5 Reputation points

2026-05-12T07:27:33.3633333+00:00
@Dora-T @Prasad-MSFT Both of these APIs are not working as expected in my case. I am using the exact URL returned in the nextLink for both scenarios and have tested with both Application and Delegated permissions.

From Microsoft Teams, I can see that the message has over 400 replies. However:

The /replies API returns only 50 replies.

The /messages API with $expand returns up to 200 replies.

Another observation: although the documentation states that the $skip query parameter is not supported for the /replies API, it does appear to work but only within the 50-reply limit. Additionally, $skip was working for pagination a few days ago, but seems to no longer function as expected.
Soumya Ranjan Mohanty 5 Reputation points

2026-05-12T09:55:41.28+00:00

@Dora-T Which API version are you using - beta or v1.0? Have you noticed any differences between them? Neither version is working in my case.
Dora-T 13,825 Reputation points Microsoft External Staff Moderator

2026-05-13T04:00:13.08+00:00

Hi Soumya Ranjan Mohanty

Thank you for the additional details.

I was using the v1.0 endpoint in my environment.

Based on my testing, the behavior of $skip appears to be inconsistent with the current documentation, since the /replies API does not officially support OData query parameters other than $top.
Soumya Ranjan Mohanty 5 Reputation points

2026-05-18T05:09:49.42+00:00

@Dora-T @Prasad-MSFT Could you please share an update on this issue? It is currently affecting our Production system. Also, is there an appropriate channel to escalate this further? The API seems to have stopped working unexpectedly.
Dora-T 13,825 Reputation points Microsoft External Staff Moderator

2026-05-18T05:43:42.87+00:00

Hi Soumya Ranjan Mohanty

Thank you for your patience while waiting for an update. Unfortunately, I do not have any additional information to share at the moment.

Please understand that this is a user-to-user support forum. Moderators do not have backend access and cannot directly intervene in Microsoft products. We can only provide technical guidance and best-practice recommendations based on publicly available information and reported behavior.

Since this is currently affecting your production environment and may require deeper investigation, you may consider contacting Microsoft Unified Support (paid support ticket) for more in-depth assistance and to receive support as quickly as possible.

Thank you for your understanding.

Hi @Prasad-MSFT , Is there any update from your team?
Prasad-MSFT 10,491 Reputation points Microsoft External Staff Moderator

2026-05-20T11:48:32.1533333+00:00

Hi Soumya Ranjan Mohanty, Giles Holmes we have raised an ICM for this issue and engineering team is looking into it. We will inform you once we have further update. Thanks!
Prasad-MSFT 10,491 Reputation points Microsoft External Staff Moderator

2026-05-26T05:49:30.5666667+00:00

Hi Soumya Ranjan Mohanty, Giles Holmes engineering team need below details for further trouble shooting. So could you please provide the missing tracing info for troubleshooting: the client-request-ids, timestamps, and URLs of the requests?
Giles Holmes 5 Reputation points

2026-05-26T14:40:58.3566667+00:00

[Moderator note: personal info removed]

client-request-id: [Moderator note: personal info removed]

timestamp: Tue, 26 May 2026 15:05:46 GMT

LINKS TO URL (for next request):
[Moderator note: personal info removed] ,

client-request-id: [Moderator note: personal info removed]

timestamp: Tue, 26 May 2026 15:07:42 GMT

response:
{

"@odata.context": "https://graph.microsoft.com/v1.0/$metadata#teams('``[Moderator note: personal info removed]``')/channels('``[Moderator note: personal info removed] ``')/messages('``[Moderator note: personal info removed] ``')/replies",

"@odata.count": 0,

"value": []

}

There are about a hundred replies here so it should loop 5 times. There's no response, however.
Dora-T 13,825 Reputation points Microsoft External Staff Moderator

2026-05-27T07:51:47.3+00:00

Hi Giles Holmes

Thank you again for sharing the detailed tracing information. This is very helpful for the investigation.

Since this is a public forum, I may need to modify your comment to help hide the personal or sensitive information included in the description.

Please create a new thread and tag @Prasad-MSFT there. He should then be able to reach out to you via private message so you can safely share the tracing details with him directly.

Thank you very much for your cooperation and understanding.

Best regards,
Soumya Ranjan Mohanty 5 Reputation points

2026-05-27T07:54:04.08+00:00

@Prasad-MSFT I have created a separate ticket with Microsoft support. Thank you for your follow up here.
Giles Holmes 5 Reputation points

2026-05-27T17:43:26.1333333+00:00

What do you mean by new thread? Can @Prasad-MSFT not contact me from here?
Dora-T 13,825 Reputation points Microsoft External Staff Moderator

2026-05-28T06:57:05.1033333+00:00

Hi Giles Holmes

What I meant was creating a new thread on this forum regarding the same issue and tagging @Prasad-MSFT in the post. After that, Prasad should be able to send you a private message, and you can then securely provide the tracing details and other information needed for the investigation.

For your reference: Ask a question on Microsoft Q&A | Microsoft Learn

Since this is a public forum, this would help avoid exposing personal, tenant, or organization-related information publicly.

Thank you again for your understanding and cooperation.
Teddie-D 16,800 Reputation points Microsoft External Staff Moderator

2026-05-29T00:56:01.15+00:00

Hi @Prasad-MSFT
Please review Giles Holmes's detailed logs in the private message within this thread MSTeams v1.0 Graph API replies endpoint pagination with skiptoken yields no results - Microsoft Q&A
Giles Holmes 5 Reputation points

2026-06-03T17:24:23.31+00:00

Has any progress been made here?
Teddie-D 16,800 Reputation points Microsoft External Staff Moderator

2026-06-04T08:32:57.8666667+00:00

Hi @Prasad-MSFT
Please collect the detailed tracing information from the Giles Holmes's private message and upload it to ICM so the team can proceed with troubleshooting.
Giles Holmes 5 Reputation points

2026-06-04T16:34:31.8466667+00:00

We also have replicated the same issue in the beta branch of the api call.

Share via

Issue with Pagination for Channel Message Replies using Microsoft Graph API ($skipToken returning empty results)

1 answer

Your answer