Hi Team, We have a customer experiencing timeout ...
# gooddata-cloud
j
Hi Team, We have a customer experiencing timeout issues when exporting a report workspace ID
f070546b-cc1a-4c8e-b216-ef3a3065016d
We had this problem before and it was related to the query that fetches users to be selected for the input field, and a fix was applied but now it seems the issue is back? May I have someone taking a look at this with some urgency please.
k
I'm sorry, but the knowledge sources do not contain enough information to directly investigate or confirm the specific issue you're describing for workspace
f070546b-cc1a-4c8e-b216-ef3a3065016d
, nor do they document the previous fix related to the user-fetching query for the scheduled export input field. However, based on a closely related case in the community, there is a documented instance where the "Create new scheduled export" dialog loaded indefinitely in an embedded environment because the system was making repeated requests to fetch users (1,000 per page), and the organization had a very large number of users (~400k). This caused the UI to hang. [Scheduled export loading] This sounds consistent with what you're describing. Here's what I'd recommend: 1. Open an urgent support ticket at support.gooddata.com and include: ◦ Workspace ID:
f070546b-cc1a-4c8e-b216-ef3a3065016d
◦ A reference to the previous fix that was applied for the user-fetching query issue, so the support team can check if the same regression has occurred ◦ Any trace IDs from failing requests (visible in browser DevTools → Network tab) ◦ A HAR file if possible 1. Confirm whether the issue is isolated to the embedded environment or also occurs in the GoodData UI directly. 2. Check the GoodData status page at support.gooddata.com for any active incidents in your region. Since you've indicated this is a regression of a previously fixed issue, explicitly referencing the prior fix when contacting support will help the team prioritize and investigate more efficiently. I'm not able to look up logs or trace IDs directly from here, so engaging GoodData Support is the fastest path to resolution. 👍 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.
s
Hi Jhonatan, I'm looking into it internally. Can you please share a link to that report? Feel free to use DM. Thanks in advance.
j
this is the dashboard name Audiology Programme Reporting learnamp.cloud.gooddata.com/workspace/…/dashboards#/dashboard/…/…
👀 1
s
I tested it directly through the GD portal, and it took about 2-3 minutes to load. Have you tried this on embedded? Does it take around 10 minutes to load, as you said in the previous thread?
j
the time to load could have been reduced but it's still pretty bad but there is another issue, when clicking around the input fields, the page freezes, this has happened even directly in gooddata
👀 1
try changing recipients for instance, the issue should occur
s
Thanks for the details, Jhonatan. I will check it myself and report to our developers. I will keep you updated.
I have reproduced the issue and reported it to our developers. I will let you know as soon as I get some information from them.
j
thanks Shamil
s
Hi Jhonatan, In the meantime, two workarounds so you're not stuck: 1. If this is for an embedded page: set a fixed export recipient with the SDK or the recipient URL parameter (iframe). Note this only works for embedded, not the native GoodData UI. gooddata.ai/docs/…/embed-dashboard-via-iframe#… 2. Either way: create the export definition and scheduled automation directly via API gooddata.ai/docs/…/scheduled-exports#… Quick question: is this blocking a scheduled report right now, or manageable for the moment?
Hi Jhonatan, Happy to say that we have released the fix. I have tested it in your project using our admin account, and it works well. Let us know if there is anything else we can help you with.
j
Hi Shamil, thanks for this, we'll be testing and let you know!
👍 1
s
Hi Jhonatan, Have you tested it? Can you confirm it is fixed?
j
hi there, yes it did fix the issue!
s
Thanks for the confirmation, Jhonatan. Happy to hear it helped!