microsoftgraph / microsoftgraph/microsoft-graph-explorer-v4

Graph Explorer is using older cached values for the endpoint text box instead of the current value

Open
#3,859 0 comments 0 reactions 1 assignee View on GitHub

@Highbury1993 is already working on this.

Since Jul 16, 2025.

Area: Query input Triaged-Unassigned
Dominant language
TypeScript
Stars
260
Forks
110
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
The Graph Explorer is using cached strings for the endpoint textbox when making calls in some cases. Editing the endpoint with further details will not make the call given, and using the version dropdown to switch between v1.0 and beta will revert the text to the previous value.

To Reproduce
One example (I'm sure there are others):

  1. Go to the Graph Explorer and set up a call to beta/me/calendars. As expected, you'll get the calendar list.
  2. Now grab a calendar ID from that list and paste it into the endpoint text box so you are making a call to beta/me/calendars/{calendarId}. Execute the call and you'll see that you're getting the calendar list, not the singular calendar. The @odata.contxt value shows the old call being made without the calendarId.

Now use the version dropdown to the left of the endpoint text box to switch to v1.0. The text will revert to the /me/calendars call and the calendar ID is removed. Paste the calendarId into the call again, try again, and see the same result. You get the calendar list. Switch back to beta and the calendar ID is wiped out again.

However, if you manually edit the version in the endpoint to v1.0/beta, it will work correctly and you will then be able to switch between versions with the dropdown without issue.

Expected behavior
Graph Explorer should always be using the value in the endpoint text box. It should never erase data when switching between API versions.

Desktop (please complete the following information):

  • OS: Macos 14.5
  • Browser: Chrome
  • Version: 137.0.7151.56

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.