microsoftgraph / microsoftgraph/microsoft-graph-explorer-v4
HTTP Internal Server Error 500 When Subsequently Retrieving @odata property (@odata.nextLink) By Clicking Links on https://graph.microsoft.com/v1.0/applications/delta Running Query
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 260
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When running https://graph.microsoft.com/v1.0/applications/delta query on Graph Explorer (https://developer.microsoft.com/en-us/graph/graph-explorer), to retrieve subsequent results (for additional records) - on Response Preview tab, by clicking This response contains an @odata property. @odata.nextLink Click here to follow the link - results would keep displaying however at some point, it returns Internal Server Error - 500:
{
"error": {
"code": "InternalServerError",
"message": "Error while processing response.",
"innerError": {
"date": "2025-12-24T08:09:39",
"request-id": "04e33019-0af2-4b13-8fc1-5587e8b27d25",
"client-request-id": "14e08d36-9359-e791-8c56-5fc3e16d9ad3"
}
}
}
To Reproduce
Steps to reproduce the behavior:
- Go to https://developer.microsoft.com/en-us/graph/graph-explorer and paste https://graph.microsoft.com/v1.0/applications/delta on GET v1.0 query field and click Run Query button
- Upon the first response, we would get OK 200, and on Response Preview tab, there are two things:
a. Information Display = This response contains an @odata property. @odata.nextLink Click here to follow the link.
b. Response result in json format - notice $skiptoken token itself.
Click Click here to follow the link._ - To retrieve the subsequent results, keep clicking Click here to follow the link address.
- What we understand, each iteration would retrieve 200 records, and if we do require to retrieve for another 200 records, we would just need to keep clicking this Click here to follow the link address.
- At some points, we would be getting Internal Server Error - 500 display.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. Windows 11]
- Browser [e.g. Google Chrome ]
- Version [e.g. 143.0.7499.169]
Additional context
Add any other context about the problem here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in Graph Explorer with the applications/delta endpoint and repeatedly following the @odata.nextLink in Response Preview. The report names no repository files, tests, or implementation entry points, and completion criteria for addressing the server error are not established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100