Qlik Replicate CDC Start Point Behavior

[ETORRES]

Hi Support;

During reconciliation it was observed that a CDC start did not go back far enough.  So, we attempted to restart the CDC task from a specific point in time (April 27, 2026). Although the correct date and time were selected in the task settings, the task did not start from the expected journal receiver for that timeframe. Instead, it resumed from a later position.

[Rahul_Kale]

Hello ETORRES,

Thank you for reaching out to the Qlik community.
 

It seems that your CDC task didn't restart from April 27 because the system didn't align the restart position with the intended journal receiver/sequence. To help you with this issue, could you please confirm the source and destination details so we can check accordingly?

[SachinB]

Hello @ETORRES ,

To investigate this behaviour further, we would require the task logs to verify the exact point from which the CDC task resumed. We recommend creating a support case and sharing the relevant task logs so we can analyse why the task did not start from the expected journal receiver for the selected timeframe.

Regards,
Sachin B

[ETORRES]

ok, thanks. Someone shares this information with me: 

Reason

Qlik Replicate stores its last processed position in a local task state (checkpoint).

When the task is restarted:

• If this saved state exists, the task automatically resumes from that point
• The selected date in the UI is not applied in this situation

In this case, the task had previously progressed beyond April 27 and saved that later position. As a result, it resumed from that point rather than reprocessing from the selected date.

[john_wang]

Hello @ETORRES ,

To clarify, there are different start modes in Qlik Replicate:

1. Resume

   If the task was stopped and then started up again using Resume Processing... (see the start method below), the task automatically continues from the previously saved stream position, as you mentioned.

   

2. Advanced → From Date and Time (see screenshot below)

   In this mode, the task ignores the stored stream position and re-captures changes starting from the specified journal position/date and time. 

   

   If Replicate instead started capturing from a later position than expected, we would need more detailed information for further investigation. Turn on SOURCE_CAPTURE to Verbose will help.

Regards.

John.

[ETORRES]

Thanks John, excellent support.