failed to apply bulk into audit table?

[MoeE]

Hi support,

I hope you are doing good. I wanted to post here just in case someone knew anything about this issue. It looks like Replicate is failing to apply changes to the audit table. This happened 3 days ago and since, the table almost appears as if it is in one-by-one mode, and the latency is almost 3 days. weird. Has anyone seen this before?

Regards,

Mohammed

[john_wang]

Hello Mohammed, @MoeE 

Thanks for reaching out to Qlik Community!

It seems the query timed out after 2 minutes, would you please add the internal parameter executeTimeout to the target endpoint and set the value to a reasonable value eg 300 (seconds) to see if the problem is solved.

Thanks,

John.

[MoeE]

Hi John,

We increased the timeout settings, and slowly the tables are starting to be picked up again. I will keep monitoring. 

generally, is there a particular cause to these timeouts? etc target endpoint is overloaded/network speeds/replicate not sending the changes? Also how exactly does the query timeout occur, as in what exactly is timing out? The apply operation on the target side?

Thanks,

Mohammed

[john_wang]

Hello Mohammed, @MoeE 

You are correct—there are several factors that can cause an update query to time out, as you've mentioned. Generally, Qlik Replicate sends the query to the target database (e.g., INSERT INTO ... SELECT FROM, MERGE, etc.). If the query doesn't complete within a specified time, Qlik Replicate considers it a timeout. This time limit can be adjusted through an internal parameter.

Hope this helps.

John.