We have an interesting problem with one (only one) of our many visualizations. It renders without issue in the cloud portal in the Analyze tab when we select it from the "Open" dropdown. However, in our embedded iframe in our customer facing web application, where we have embedded the entire analyzer /analyze/embedded/#/blabla and use the same "Open" dropdown and select this particular visualization its giving a message "SORRY, WE CANNOT FIND THIS VISUALIZATION". It seems to be something out of our control. No rush on this one.

This is an interesting case — the visualization works in the native GoodData UI but fails with "SORRY, WE CANNOT FIND THIS VISUALIZATION" only in the embedded Analytical Designer iframe. Based on the knowledge sources, here are the most likely causes and recommended steps: Most Likely Causes 1. Invalid identifier in the visualization definition — A known cause of this exact error is when the visualization object contains an incorrect or malformed identifier (e.g., a ranking filter with an ID that doesn't end in an alpha character). This can cause the Analytical Designer to report the visualization as non-existent, even though it exists and is queryable via the API. [Viz switcher issue] 2. LDM mapping issues — If any attributes or labels referenced by the visualization have mapping warnings in the LDM, this can cause failures in certain contexts. [Dashboards failing – LDM label issue] 3. Non-existent or inaccessible identifiers in filters — The visualization may reference attributes or filter contexts that are inaccessible or no longer valid, which can surface differently in the embedded environment. [Cannot find visualization] Recommended Steps 1. Inspect the visualization object definition via the API endpoint:GET /api/v1/entities/workspaces/{workspaceId}/visualizationObjects/{insightId}Check all identifiers — especially any filter contexts (including ranking filters) — for malformed or non-existent IDs. [Cannot find visualization] 2. Check the LDM for any warnings in the mapping tab for attributes used in this specific visualization. 3. Capture a Trace ID from the browser DevTools (Network or Console tab) while reproducing the error in the embedded iframe, and share it with GoodData Support — this is essential for them to locate the server-side error in logs. [Viz errors] 4. If the issue persists, consider opening a support ticket at support.gooddata.com with the Trace ID, workspace/visualization links, and a description of the discrepancy between the native UI and embedded behavior. The fact that it works in the native UI but not in the embedded iframe is consistent with cases where a subtle definition issue (like a malformed filter ID) causes the Analytical Designer to fail to resolve the visualization in certain rendering contexts. 👍 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.

Here is the X-Gdc-Trace-Id 6df6026c559c4fbf7d38dc88154d87d1 Viz id is def70351-3c29-4303-bf3a-a40a5f91d8b4 It occurs across all our workspaces.

Hi Jeremy, can you please send me a direct link to the dashboard via DM and also capture a HAR file and replicate the issue and also send this over to us to assist our investigation?