Hi we noticed some insights in one of our dashboards failing to load and after a while and usually the page becomes unresponsive. would appreciate your help on this.

Hi! Sorry to hear you're experiencing this. Based on your screenshot showing a "Page Unresponsive" error on a GoodData Cloud dashboard, here are the most likely causes and steps to investigate: 1. Check for Data Size Limits The page becoming unresponsive is a known symptom when visualizations hit platform limits. For example: • 500 MB data return limit:

"Reached limit of max size of data returned from data source. The limit is 500,000,000 bytes (500 MB)"

[Dashboard Freeze Case] • 100,000 row limit:

"xtab-rows: The limit for the maximum size of the dimension without metrics was exceeded. Limit: 100_000"

[Limits Hit] Try opening individual slow visualizations in Analytical Designer to see if they show an error about being too large. 2. Investigate the Slow Queries • Open a slow visualization in Analytical Designer and replace

/edit

with

/debug

in the URL — this downloads the exact SQL GoodData runs against your database. • Run that SQL directly on your database to check execution time, heavy joins, or timeouts. • Try removing metrics one by one to identify which one is the heavy driver (the first metric acts as the SQL "driver"). [Performance Debugging] 3. Check for HTTP/1.1 Connection Limits On large dashboards, browsers limit concurrent requests to ~6 per domain. If your hosting environment only supports HTTP/1.1, requests queue up and cause the UI to freeze. The fix is to ensure your server supports HTTP/2 or HTTP/3 (e.g., by placing a CDN like CloudFront in front of your app). [HTTP Limits Thread] 4. Check Dashboard Structure If your dashboard uses tabs, make sure it doesn't have both

content.layout

and

content.tabs[0].layout

defined simultaneously — this conflict can cause executions to get stuck and exceed combined size limits. The fix is to PATCH the dashboard to remove

content.layout

, keeping only

content.tabs[0].layout

. [Dashboard Layout Conflict] 5. Collect Information for Support To help GoodData Support investigate further, please gather: • Trace IDs from the Network tab in browser DevTools during a slow/failing load • A HAR file captured from Chrome DevTools during the issue • Exact timestamps (with timezone) of when the unresponsiveness occurs • Whether the issue affects all users or specific ones, and all dashboards or just this one [Support Investigation] As a quick test, try loading the same dashboard in Firefox — if it works there, the issue may be browser/Chrome-specific. Let me know what you find and feel free to share trace IDs for further investigation! 👍 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.

1. when opening the individual insights I see the same problem, nothing loads and the page becomes unresponsive (I don't see any errors) the example I checked: https://insights.aklamio.com/analyze/#/d5d40198602544e48613a66d57ed74d9/1f5a9d9e-23e3-4ef0-92da-5d7309ac7bc6/edit 2. same this for the debug mode, nothing loads. 3. will have to ask about that. 4. we don't use tabs in this dashboard 5. The issue occurred for several users all on Chrome.

Hi Amir, could you please share the link to your dashboard? I will take a look internally. Feel free to use DM in case of any sensitive information. Thank you.

hi Shamil, here: https://insights.aklamio.com/dashboards/#/workspace/d5d40198602544e48613a66d57ed74d9/dashboard/fdf657e6-2fa1-4a93-9dbb-bea2702d159e/tab/defaultTabId

Thank you for your patience, Amir. I have reviewed your dashboard using our admin access and can confirm the issue that my colleague Daniela highlighted yesterday.

The main issue here is that organization layout JSON has both

content.layout

and

content.tabs[0].layout

defined simultaneously, with identical content. Therefore the executions get stuck due to the conflicts and exceeding combined in size. The solution here is to PATCH your dashboard to remove

content.layout

entirely, keeping only

content.tabs[0].layout

. This is the correct structure for version 2 dashboards that use tabs. I’m assuming you want to keep the tabs one, but if not keep

content.layout

and remove

content.tabs

.

Please try this and let us know how it goes. Also, could you also let us know when you first encountered this problem? Was everything working as expected before this occurred? Thank you.

We're not using any tabs in this dashboard so I don't see how it would be different to any of our other dashboards. and I also don't understand the recommended fix, how do I patch a dashboard? can you guide me on that? we noticed the problem yesterday and since the teams check it regularly I assume it was working fine before then.

Thank you for the details, Amir. We are looking into it and will get back to you soon.

Sure, will keep an eye on it, if I add date filters on the insight level, would the dashboard level date filter take precedence over it? I'm wondering how it works in general when a dashboard is opened does GD fetch all data points and THEN applies the dashboard filters? or do they get applied from the beginning. If it's the first case, we might consider adding date filters for every insight to avoid heavy loads on our DB.

Hi Amir. Filters in GoodData are always applied at query time - meaning the data is scoped before it ever hits your database. GoodData never fetches everything and filters afterwards, so adding insight-level date filters would not reduce the load on your database. Regarding how dashboard and insight-level date filters interact, the behavior is as follows: • If neither the dashboard nor the insight has a date filter → no date filter is applied • If only the insight has a date filter → the insight filter is used • If only the dashboard has a date filter → the dashboard filter is used • If both have a date filter on the same date dimension → the dashboard filter takes precedence and overrides the insight filter • If both have a date filter on different date dimensions → both filters are applied simultaneously (AND logic) You can read more about this in our documentation: Use Date Filter on Dashboards

thanks for the info, the dashboard is still however problematic.especially on edit mode.

Hello Amir, This is Daniela with L2 Support. I’ve been checking the issue and I can confirm that the dashboard stays frozen. I’m currently checking this deeper and I’ll come back here with more news very soon. My apologies for all the issues.

Hi Daniela, no worries, thanks for checking

Hello Amir, Sorry for the delay here. We found the root cause of the issue and we will deploy the fix tomorrow. I’ll let you know once its in Production.

Hi Daniela, it works fine now, thanks for following it up 🙂