In practical terms, this message suggests that for a brief period, the task did not detect any new changes in the logstream staging task. The most likely explanation for this occurrence is that no new events or data updates were generated during that specific timeframe for this particular task.
It is advisable to examine the staging task in the console. By doing so, you can pinpoint the most recent time at which events were received, especially for tables associated with the child task that triggered these warnings.
This information provides valuable insights into the task's behavior and ensures you are alerted to any prolonged disruptions in data capture.
The warningchanges are not being capturedmay 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. You can confirm this by verifying that there is no data discrepancy between source and target.
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 example, the staging task has stopped writing data to the log stream files for some reason.
