Hi team, When I am using an embedded dashboard, I go to Schedule export, Create new -> it keeps loading forever, it takes a looong time to load, more than 2 minutes. Do you know what's happening, and if this is an issue on your end?

Based on the knowledge sources, there are a few known causes for slow or infinite loading in the GoodData "Scheduled exports / Create new" dialog, particularly in embedded contexts: Known Causes 1. Scheduled exports in an inconsistent/corrupt state: In one documented case, schedules on dashboards entered an inconsistent metadata state, which caused dashboards (and related UI) to hang indefinitely. The fix was to remove the problematic schedules via the API. [Schedules out of sync] 2. Platform-level incidents: There have been cases where GoodData infrastructure issues (e.g., IAD1 or DUB1 datacenter problems) caused dashboards and embedded content to spin/load indefinitely. [IAD1 outage] 3. Embedding-specific issues: Some loading problems have been observed exclusively in embedded environments (not in the GoodData UI directly), sometimes related to embedding configuration or WebComponent setup. [Embedded loading issue] Recommended Next Steps 1. Check if the issue is isolated to the embedded environment — does the "Create new" scheduled export dialog load correctly when accessed directly in the GoodData UI (not embedded)? 2. Check the GoodData status page for any active incidents in your region (IAD1 us-east-1 or DUB1 eu-west-1). 3. Capture a HAR file and any TraceIDs from your browser's Network tab while reproducing the issue — these are essential for GoodData support to investigate. 4. Open a support ticket at https://support.gooddata.com with: ◦ Your Organization ID and Workspace ID ◦ The embedding method you are using (e.g., WebComponents, SDK, iFrame) ◦ The HAR file and any TraceIDs ◦ Confirmation of whether the issue occurs in the GoodData UI directly as well The knowledge sources do not contain enough detail to confirm the exact root cause in your specific case, so engaging GoodData support with the above information is the most reliable path forward. 👍 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.

seems to be happening only on embedded

Hi Jhonatan, if this is only happening in the embedded enviornment, would you be able to send over a HAR file? Also, can you confirm if other users on different machines are experiencing the same behavior?

looking at the network logs I believe I know what could be happening, but not sure how we could sort this, it keeps making requests to fetch users (1000 per page), but we just have a LOT of users, as we as creating literally all our users in GoodData, we now have 400k users

Hi Jhonatan, I will discuss this further internally and get back to you with more details shortly

with JWT

Understood. Thank you for the confirmation

hi @Joseph Heun was there any outcomes from the issue I presented before?

Hi Jhonatan, I've just updated the internal ticket to get more information from the engineers on a fix. At this time, there is a still a workaround in place as the delay is not shown in the UI (only in the embedded enviornment). Therefore, I would like to understand the business impact this has on you and your end users?

it seems it was working better at a certain point, but I have been receiving complaints again this impacts multiple big customers we have, as they need to be able to generate exports, but the dropdown users list just takes a long time to load

Hey, Im Nic, I have been working on the Product>Customer relationship. To give some more nuance on the impact they will be looking at creating this and scheduling reports on a monthly basis to ca 100 different users. They have raised som reliability concerns as it takes up to 5-10 minutes to load the drop down of selected users. If it loads at all 🙂 Is there anything that I can do here to support a resolution?

Hey @Joseph Heun, any updates on this one?

Hi Jonathan, Thank you for your patience. Unfortunately, we don't have an update or ETA to share just yet — the internal ticket has been created, but our development team is currently focused on higher-priority tasks, so this one remains in the backlog for now. In the meantime, we'd recommend managing the affected scheduled emails directly through the platform UI as a workaround. We appreciate your understanding and will keep you posted as soon as there's any progress.

Based on our observability system, the issues you were experiencing were caused by overloaded metadata database. We’ve taken measure to improve the available resources and after monitoring the situation for a while, we believe the issue is now resolved. Can you please confirm that you have not experienced any further outages?