Hi Everyone, we noticed that Qlik CDC tables can have a somewhat significant delay with whihc entries may appear in the table.
this entry was made in the system on 2026-05-18 at ~9.16pm local time or 7.16pm UTC time.
But when this entry effectively entered the CDC table is not deductible from this screen or any other metdata (if I am not mistaken).
we were not able to fetch this etnry with our daily incremental copy job (that covers the last 26hours or so every day), even though we covered exactly this time window (header__teimstamp or TSULTMOD) with the copy job.
we were able to fetch the associated policy entry from the policy table without issues and you can see the entries there have the same header tiemstamp and TSULTMOD.
to us this only suggests that the time at which the entry appeared in the XXXXX__CT table was significantly LATER than expected (at least a few hours "too late" - so tha it was not covered by our time window).
Could you investigate:
is there a possility to see the date at which the entry enters the CDC table (I expect it cannot be HEADER__TIMSTAMP or TSULTMOD)
is there an SLA or delay limitation, guranteed by Qlik? -> if you are not aware, can you investigate that? in my view, Qlik technology needs to be able to tell us what can be the maximum time delay with whihc an entry can enter the __CT table. otherwise we're always at risk of missing an entry if we do incremental copy jobs.
This is quite a big problem for us and we would like a confirmation about how it works.
What are your source and target databases? To troubleshoot the latency issue, please enable verbose/trace logging for the PERFORMANCE and SOURCE_CAPTURE components. You can find more detailed information in the task log. If this is a high-priority issue, please open a support ticket for immediate assistance.
Regards, Desmond
Help users find answers! Do not forget to mark a solution that worked for you! If already marked, give it a thumbs up!
