Reproduction
- Create or select a deck.gl multi layer chart
- Click on 3 dots menu on top right
- Click to View Query
- Query will never finish loading
Since there are multiple charts, there will be more than one query. We should probably think on a way to show them separately or at least show a friendly feedback to the user if we can't process the query.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.11
Node version
18 or greater
Browser
Firefox
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
This looks like a real bug: the "View Query" modal is designed to handle a single query, but deck.gl multi-layer charts generate multiple queries (one per layer). When the modal receives an unexpected structure (like an array of queries instead of a single object), it hangs indefinitely instead of showing an error or handling multiple queries gracefully. There’s no user-facing error or workaround built in right now, so the modal just spins forever if it can’t process the response see code details.
Recent changes to deck.gl multi-layer chart handling (cross-filters, viewport logic, filter propagation) may have introduced or exposed this incompatibility PR #33789 PR #33769 PR #33364. There’s no documentation or open issue tracking this specific infinite loading bug, and no built-in workaround.
If you need to see the queries, you can inspect the network response for the "query" API call in your browser’s dev tools—this will show all queries as raw JSON. Otherwise, the only way to avoid the bug is to use a single-layer chart or wait for a frontend fix that properly handles multiple queries in the modal.
If you see any errors in the browser console or network tab when this happens, sharing those details could help pinpoint the exact failure point.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
