Thanks for the clarification @stbjelcevic 

The docs say the SQL Server gateway must run continuously and can resume from its previous point as long as the required source logs still exist. Is there any documented way to determine how far behind a gateway can safely fall before a full refresh is required or is that entirely governed by the SQL Server CDC/change-tracking retention configuration?

Also is there a recommended metric/event/log to monitor the gateway’s current CDC position/ lag against the old retained source log, so we can alert before the retention window is exceeded?