Fetch Timeout Issues in QuickSight Filters with Direct Query After Recent Changes

Question & Answer
, , , , , , , ,
1

I’m encountering frequent fetch timeout issues when using filters in Amazon QuickSight with direct queries. These timeouts weren’t an issue earlier, but have recently started appearing.

I’m querying data directly from an external data source (MySQL), and the timeouts are happening consistently during filter operations.

Has anyone experienced similar issues, and what would be the recommended approach to resolve these timeout errors?

Error
Error1805×910 159 KB

Any suggestions or guidance on how to handle this would be greatly appreciated!

2

Hi @isingla

Generally the issue is with the query. Have you checked if the same query works fine in the mysql database in Mysql workbench?

I have had issues with the incremental refresh getting slower on my datasets and sometimes fails as the datasize grew. So, you may need to review your query and see if there are improvements in the query possible.

Regards,
Giri

3

Hi @isingla,
It’s been awhile since we last heard from you; did you have any additional questions regarding your initial topic?

If we do not hear back within the next 3 business days, I’ll go ahead and close out this topic.

Thank you!

4

Hi @isingla,
Since we haven’t heard back, I’ll go ahead and close out this topic. However, if you have any additional questions, feel free to create a new post in the community and link this discussion for relevant information if needed.

Thank you!