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

Announcements
ALERT: The support homepage carousel is not displaying. We are working toward a resolution.

Qlik Replicate task failure caused by future-dated LogStream data

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

Qlik Replicate task failure caused by future-dated LogStream data

Last Update:

Jan 8, 2026 10:07:20 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jan 8, 2026 10:07:20 AM

Changing the system time to a future date while a LogStream task is running leads to task errors.

Example errors:

Staging task

[TASK_MANAGER ]I: Task 'staging task' running CDC only in fresh start mode
[TARGET_APPLY ]I: Timeline is 20251211134943253089
[TARGET_LOAD ]I: Timeline is 20251231100205831444

Replication task

[TASK_MANAGER ]I: Task 'replication task' running full load and CDC in fresh start mode
[STREAM_COMPONEN ]I: Timeline is 20251212174220223963 (ar_cdc_channel.c:552)
[SERVER ]I: The process stopped (server.c:2589)

[TASK_MANAGER ]W: Task 'replication task' encountered a recoverable error

[SERVER ]I: Stop server request received internally

 

Resolution

The creation of LogStream data with a future date is caused by manual intervention. This scenario is outside the scope of Qlik Replicate’s intended test scenarios and is not covered under support.

The best action would be to reload the parent staging tasks and reload the child replication task.

 

Cause

After the system time was changed to a future date and the task was executed, a future-dated directory was created. When the system time was restored and the task was reloaded, the future-dated directory remained and appeared to have caused the replication task error.

 

Environment

  • Qlik Replicate
Labels (1)
Version history
Last update:
a week ago
Updated by: