Qlik Replicate Transaction Consistency Timeout occurred. xtransactions are still open

Michael_Litz — Thu, 28 Jul 2022 13:17:38 GMT

Running a task causes the following to be logged:

W: Transaction consistency timeout occurred. x transactions are still open

The message indicates that the Qlik Replicate process exceeded the timeout wait period set.

The setting can be configured in the Qlik Replicate Task Settings (see Full Load Tuning😞

Go to Full Load
Locate Full Load Tuning
Choose Transaction consistency timeout (seconds):

This will not cause the task to fail but could result in missing data.

What does this mean? When the task starts, it will start reading the source transaction log first, looking for a point where there are no open transactions. When the task reads the log and there are open transactions, it will wait for them to be committed or rolled back. If the time to commit is longer than "Transaction consistency timeout" value, then the task will start anyway and changes from the open transactions are not captured.

Therefore it is a best practice to start a full load during quiet time on the source database. You also have the option to increase the "Transaction consistency timeout (seconds):" parameter on the Full Load Tuning screen so that Replicate will wait longer for transactions to complete or roll back before the full load begins.

Re: Qlik Replicate Transaction Consistency Timeout occurred. xtransactions are still open

MoeE — Fri, 27 Mar 2026 04:17:12 GMT

Hi,

How does this result in missing data?

Thanks,

Mohammed

article Qlik Replicate Transaction Consistency Timeout occurred. xtransactions are still open in Official Support Articles

Qlik Replicate Transaction Consistency Timeout occurred. xtransactions are still open

Re: Qlik Replicate Transaction Consistency Timeout occurred. xtransactions are still open