Hello GoodData support One of our customers received this scheduled export error notification, which looks to be a problem with the GoodData API. Could you please investigate, screenshot has a traceId.

Hello! Thank you for reaching out. I can see from the screenshot that your customer received a "Scheduled export failed" notification with the following details: • Error:

UNAVAILABLE: DNS failed for tiger-tabular-exporter-headless; caused by: tiger-tabular-exporter-headless: Name or service not known

• Trace ID:

69dd1309dde247989eb3848f395af8f7

This error indicates a DNS resolution failure for the internal tabular export service, which points to a platform-side infrastructure issue rather than a configuration problem on your end. I'm not able to look up this specific Trace ID in logs from here. To get this properly investigated, please take the following steps: 1. Open a support ticket at https://support.gooddata.com, including: ◦ The Trace ID:

69dd1309dde247989eb3848f395af8f7

◦ Your Organization ID and Workspace ID ◦ A description of the impact and when the issue started ◦ The screenshot you've shared 1. Check the GoodData Cloud status page (accessible via the support portal) to see if there are any ongoing incidents affecting your region that may explain this DNS failure. [Export incident handling] 2. In the meantime, you can check whether the export succeeds if triggered manually from the UI, which can help narrow down whether this is a transient infrastructure issue or something more persistent. [Scheduled export timeout] GoodData Support will be able to look up the Trace ID in their logs and confirm the root cause. Apologies for the inconvenience your customer has experienced. 👍 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.

Hi Eoghan, Thanks for sending this, happy to help. We are currently checking this and will get back to you as soon as possible. Can you also confirm if this affects all users in the workspace?

Thanks Yvonne. I'll need to follow up with our Customer Success team to see if this is impacting all the workspace users - let you know once I have an answer.

Hi Eoghan, Thank you for your patience. I can confirm that, after further investigation, the timeframe you reported aligns with a temporary disruption we experienced yesterday that affected scheduled exports. Our engineering team resolved the issue promptly, and we have not observed any further problems since. Everything should now be functioning as expected. I sincerely apologize for any inconvenience this may have caused. Could you please confirm whether the scheduled exports are now working correctly?

Hi Yvonne. Good to hear that issue has been resolved and is not expected to be recurring. The scheduled export in question is sent out weekly, so I can't confirm delivery until it runs again next week. However, other scheduled exports for that workspace and other workspaces have executed successfully since this problem, and we haven't heard of any similar failures from other customers. Thanks for your help!