Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.

Qlik Replicate: Query timeout expired

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Steve_Nguyen
Support
Support

Qlik Replicate: Query timeout expired

Last Update:

Jun 20, 2023 5:10:36 AM

Updated By:

Sonja_Bauernfeind

Created date:

Feb 1, 2021 2:32:52 PM

A Qlik Replicate task fails with error

Query timeout expired

Resolution

The error occurs when Qlik Replicate is working on a query to the source or target and the query takes longer than anticipated, leading to the timeout. 

Edit the source or target endpoint and within the Advanced properties and add a new Internal Parameter named cdcTimeout.

  1. Stop the task.
  2. Open source or target endpoint depending on the error from the query source or target and add the following Internal Parameter:

    cdcTimeout (default 600); (some endpoints do not have this value)
    executeTimeout (default 60)
    loadTimeout (default 1200).

    Try 10x the default value. Values are in seconds.

    See Qlik Replicate: How to set Internal Parameters and what are they for? for more information.

  3. Save the endpoint
  4. Try to resume task and see if we still have a timeout issue.

 

Environment

Qlik Replicate 

 

Labels (1)
Comments
charlesrinaldini_colas

This does not appear to change anything on the Microsoft Azure Databricks Delta endpoint. On a full load, query execution times out after 60 seconds not matter what. This completely negates the use of this product if we cannot load our larger tables. 

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @charlesrinaldini_colas 

It sounds like you need assistance with this particular setup. Please contact support so that we can help you accordingly! 

All the best,
Sonja 

Mark_CR
Contributor
Contributor

Can this be set at the endpoint level and have it apply to all the tasks that use that endpoint?

Dana_Baldwin
Support
Support

Yes @Mark_CR, these internal parameters are set at the endpoint level and are used for every task that uses that endpoint. Tasks need to be stopped and resumed after setting these parameters before they become effective (endpoint parameters are read & processed upon task startup).

Thanks,

Dana

Version history
Last update:
‎2023-06-20 05:10 AM
Updated by: