microsoftgraph / microsoftgraph/microsoft-graph-explorer-v4

GE intermittently ignores current request and returns stale response from previous query

Open
#4,035 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Describe the bug
Graph Explorer occasionally returns results from a previous successful request instead of executing the current request. This results in inconsistent behaviour where certain endpoints return outdated or incorrect data, while others work as expected within the same session.

To Reproduce
PS: The issue is intermittent so might not be easy to repro.

Run a successful request (e.g. /users, /groups, or /applications)
Modify the query to a different endpoint (e.g. another resource or different parameters)
Execute the new request
Observe that Graph Explorer may return results from the previous successful query instead of the current request

Expected behavior
Each request should be executed independently, and the response should always correspond to the currently submitted query.

Screenshots
https://github.com/user-attachments/assets/4c2bc005-e62c-4bb7-bc30-e83c8b816d2e

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser: Chrome

Additional context

  • The issue appears intermittently and is not tied to a specific endpoint.
  • In the same session, some endpoints (e.g. users, groups, applications) may work correctly while others return stale results.
  • Refreshing the browser or closing and reopening the tab can temporarily resolve the issue.
  • The issue can be disruptive when testing APIs, as it creates uncertainty about whether the response reflects the intended request.

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.

Research direction

Start by reproducing the issue in Graph Explorer with successive /users, /groups, and /applications requests, then compare the submitted query with the displayed response across refreshes. No source file or test is named in the issue; done means each submitted request consistently produces its own response without stale results.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, redux, typescript
Domain
api, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.