Query timed out for table/query

Last updated on Dec 16, 2022
Error Message Text(s) Job is failing repeatedly with error: Query timed out for table/query:

Potential Causes

In case of log-based Pipelines, while incremental (new and updated) data is fetched using the database logs, Hevo uses the most optimal query mode based on your Source objects/tables to ingest the historical data. Historical data is data that is already existing in your Source at the time of creation of the Pipeline.

At times, the query run by the selected query mode may fail due to some constraints at the Source side, such as, timeout due to no indexing or high CPU/memory utilization.

Suggested Action(s)

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Dec-16-2022 NA New document.

Tell us what went wrong