How to avoid "Changes are not being captured" when Log Stream Staging task encounter error?

[vinci_wu]

 We use the replicate workflow: One Log Stream Staging task capture to log stream staging folder, then two task  replicate to target database.    When there is some maintenance in source db or  some network issues, Log Stream Staging task encounter error, then two replicate will encounter   "Changes are not being captured" .  Then replicate will loss some data.

We need to reload all tables. 

How to avoid "Changes are not being captured"?  

By the way, the source db is Oracle active standby.

[Gerald_U]

Hello,

The warning changes are not being captured may be caused by 2 things:

Reason 1

Valid scenario, where parent/log stream tasks actually did not receive any data from the source, for example, if the changes currently happening on the source are not related to the tables in the task.

Reason 2

Error scenario, where parent/log stream task encountered an issue and parent/log stream task continues to run without throwing an error. Check the staging task if there is an error during the same time frame when you received the warning on the replication task.

For the second scenario, please open a support case for assistance.