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)

• If you are able to successfully execute other SQL queries on your Source, try switching to a different query mode for the Pipeline or the object. Read How do I change the query mode for my Pipeline? for steps to do this.

Revision History