Hi @ShivangiB1  Even though dbo_test_table was created by running lakeflowSetupChangeDataCapture, Lakeflow does NOT consider it a Lakeflow-managed instance unless it follows the lakeflow_ naming pattern.

So Created by lakeflowSetupChangeDataCapture ≠ Managed by Lakeflow
Managed by Lakeflow ⇒ Must have lakeflow_ prefix
If it does not have the prefix, Lakeflow will not monitor or control it, even if the stored procedure created it.

Even if dbo_test_table was created via lakeflowSetupChangeDataCapture, Lakeflow does not manage or monitor it unless the capture instance follows the lakeflow_ naming convention. The prefix is the sole mechanism Lakeflow uses to determine ownership and lifecycle management, which is why a second instance is created and monitored.