Hi GD Support. We've noticed that after editing a ...
# gooddata-cloud
e
Hi GD Support. We've noticed that after editing a Dashboard via embed, the Dashboard does not display the edit updates without a forced refresh - either full page or navigating to other dashboard and back to the updated one. Has anyone else reported this? Could you please investigate if it is a regression bug?
1
k
I'm sorry, but the knowledge sources do not contain enough information to confirm whether this specific issue — dashboard edits via embed not reflecting without a forced refresh — has been previously reported as a known or regression bug. That said, there are a few related observations from the community that may be relevant to your situation: 1. Caching behavior GoodData's caching mechanism can cause dashboards to display stale data after updates. The cache is not automatically invalidated on a schedule — it requires explicit cache reload via API, Python SDK, or the data source UI. [Cache Management] 2. Browser-level caching in embedded dashboards Even after backend cache invalidation, the frontend (especially in iframe-embedded contexts) can still serve stale content due to browser-level caching (service workers, LocalStorage, HTTP cache, etc.). A hard reload or clearing cookies may be needed for clients to see updated data. [Frontend cache staleness] 3. Embedded dashboard data loading issues There have been reports of embedded dashboards failing to load or display updated data without a refresh or resize, particularly after filter changes. [Embedded dashboard issue] Recommended next steps: To help GoodData Support investigate whether this is a regression bug, please provide: • TraceIDs from the browser Network tab when the issue occurs • A HAR file captured while reproducing the issue in the embedded environment • Details on your embedding method (iframe, Web Components, React SDK) and relevant code snippet • Confirmation of whether the issue occurs only in the embedded context or also directly in the GoodData UI • Your data source caching configuration (e.g., "Optimized for speed and savings" vs. "Optimize for real-time data") GoodData Support monitors this channel and will be able to investigate further once they have these details. 👍 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.
e
We embed via iframe. We've only been able to reproduce the problem in the embedded context. We use 'optimize for speed and savings' for data source caching. This problem is not data related. An example is that if a widget is added to a dashboard and then dashboard is saved, the widget will not display in the read version of the dashboard without forced refresh.
j
Hello Eoghan, we are currently looking into this behavior, but could you confirm possibly when this changed for you?
Also, could you send over a HAR file capturing the add-widget-and-save reproduction along with the exact iframe embed URL you're using (specifically whether it starts with /dashboards/embedded/ or /embedded/)?
e
Thanks Joseph. We noticed this yesterday. It was raised by an internal user - developer colleague - not a customer of ours.
This is the format of the iframe URL we're using.
https://{goodDataDomain}/appLogin?redirectTo=/embedded/workspace/{workspaceId}/dashboards/#/dashboard/{dashboardId}?showNavigation=false
j
Thanks for this. Is there any chance we could get the HAR file too? It would really help with troubleshooting here
Hi Eoghan, I'm actually able to reproduce the same behavior now. I'm going to open an internal ticket with engineering.
e
Great thanks Joseph - sorry I couldn't get you that HAR file sooner to help out.
@Joseph Heun any update on the status of this issue?
m
Hi Eoghan, sorry for the delay in getting back to you. Unfortunately, there isn’t much we can share with you at this time. Due to more pressing issues our Engineers have been working on - However, I am going to go ahead and update our internal ticket with our Engineers and see if we can get some movement on this one for you. Thanks for the ongoing patience here!
e
Thanks for the update @Michael Ullock, appreciate it!