Kept getting DATA_SOURCE_TIMEOUT error message

Q&A
,
1

Hey team,

Are there any known issues with QuickSight (QS) data ingestion today?

I keep getting a DATA_SOURCE_TIMEOUT error on datasets that were previously working fine with no changes. The issue is intermittent, as it failed a few hours ago, worked for an hour, and is now failing again.

Could someone let me know if this is a known platform issue, or if there’s something specific I should troubleshoot on my side? Thanks!

2

Hi @irinaaaaa

Thank you for reporting the intermittent DATA_SOURCE_TIMEOUT errors. Since there were no changes on your side and the behavior is intermittent, this may be related to an upstream service issue.

We recommend checking the following for any active advisories in your region:

AWS Health Dashboard - for service-wide status.
AWS Personal Health Dashboard - for account-specific notifications.

3

Hey @Xclipse,

Thanks for sharing. QS has looked very healthy for the past week. Now, I wonder if it’s probably because I’m not using it accurately.

Whenever I update a query (CUSTOM SQL) in my dataset, the first attempt always fails. My current workaround is to revert to the old query, apply it, and then try the update again. It works, but it’s a bit tedious.

Do you know if there’s a more efficient way to handle updates with Custom SQL? Appreciate any tips!

4

Hi @irinaaaaa,

Thank you for the additional details. The behavior you’re describing, where the first attempt to update a Custom SQL query fails but subsequent attempts succeed, is a known pattern. When you modify a Custom SQL query, Quick Suite validates it against the data source, and this initial validation can timeout due to connection warm-up or query complexity.

Tips to avoid the revert-and-retry workaround:

  1. Preview before applying: Use the Preview data option after editing the SQL to warm up the connection before saving.
  2. Keep the query window open: If the first save fails, simply click Save again without reverting. The connection is often already warmed up from the failed attempt.
  3. Simplify validation: Temporarily add a LIMIT 1 to validate the schema quickly, then remove it once saved successfully.
  4. Check your data source timeout quotas: Depending on your underlying source, the validation timeout may be as low as 45 seconds.

Please check the following relevant documentation, which might be helpful for you.

5

Hi @irinaaaaa,

Just checking back in since this thread hasn’t received a response in a while. Was Xclipse’s most recent reply helpful to you and/or were you able to find a solution yourself in the meantime? Please help the community by marking this answer as “Solution” or following up in general within the next 3 business days!

Thanks!

6

Hi @irinaaaaa,

Since I haven’t received any further updates from you, I’ll treat this inquiry as complete for now. If you have any additional questions, feel free to create a new post in the community and link this discussion for context.

Thanks!