Hello, I am trying to obtain the underlying query from our GoodData widget and when editing in GoodData the URL used to show

/edit

which could be changed to

/debug

to achieve this. I am no longer seeing

/edit

in the URL when I click the edit button and adding

/debug

at the end of the URL isn't triggering a download of the file. Can you help me understand how to obtain the debug file with the underlying SQL query for debugging?

You can still get the debug ZIP with the underlying SQL; a few things to check and alternative ways to call it: 1. Use

/debug

from Analytical Designer (still supported) ◦ Open the visualization in Analyze (Analytical Designer), not from the dashboard. ◦ In the URL, the last segment is normally

/edit

(e.g. `.../analyze/#/`workspace`/`insight-id`/edit`). ◦ Replace that last part with

/debug

→ `.../analyze/#/`workspace`/`insight-id`/debug`. ◦ This does *not open a page*; it should trigger a file download (a ZIP, often named

explainAfm.zip

) that contains

report.json.qt.opt.sql

with the SQL query. [Check query debug; See executed SQL] 2. If

/debug

“does nothing” Known reasons from the sources: ◦ The file is downloaded silently to your browser’s Downloads folder (no new tab). Users sometimes think it “didn’t work” because nothing opens. [Check query debug] ◦ In some cases with very large/complex models, the backend struggles to build the full debug package and the plain

/debug

call fails. In that case, you can add a parameter to request only SQL: ▪︎ Use:

.../debug?explainType=SQL

This is explicitly mentioned as a workaround when

/debug

alone fails. [Large model workaround] 3. If you no longer see

/edit

in the URL The sources don’t describe a new URL format, but they consistently assume that: ◦ You must be on the Analyze view of an insight (not just the dashboard view of a widget). ◦ Once there, the URL ends with

/edit

, which you then replace. [See executed SQL; AFM explain usage] If, after opening the widget in Analyze, you still don’t see

/edit

and

/debug

or

/debug?explainType=SQL

doesn’t download anything (and nothing appears in your Downloads), the knowledge sources don’t provide more detail on that specific behavior. In that case, the next step is to capture a traceId from the browser DevTools/network error and contact GoodData Support so they can check backend logs. [Error /debug case] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

Hi Nick, Works for me.. don't you just use

explore from here

on Dashboard instead of going to EDIT mode, or opening the visualization directly in Analyzer?

Hi Julius, yes its working for me as well now. Thanks!