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.
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):
Additional context