https://community.databricks.com/t5/data-engineering/lakeflow-connect-sql-server-snapshots-firing-outside-configured/m-p/154686#M54125 <P>Has anyone else seen full refresh snapshots trigger outside of their configured refresh window in Lakeflow Connect?</P><P>Here's our situation:</P><P>- We have a full refresh window configured to restrict snapshot operations to off-hours<BR />- On at least one occasion, a snapshot started outside of that window — during business hours<BR />- This caused unintended load on our SQL Server source during peak usage</P><P>The docs are clear that snapshots should only start during the next available time in the configured window, so this feels like unintended behavior. I'm still investigating whether there's a specific trigger (e.g. auto full refresh policy, a pipeline retry) that might bypass the window, but so far I haven't been able to pin down a consistent cause.</P><P>Has anyone else observed this? And if so, have you found any conditions that reliably cause a snapshot to ignore the configured window?</P><P>Would love to know if this is a known bug or if there's something in our configuration we should be looking at.</P> Wed, 15 Apr 2026 21:51:23 GMT lrm_data 2026-04-15T21:51:23Z https://community.databricks.com/t5/data-engineering/lakeflow-connect-sql-server-snapshots-firing-outside-configured/m-p/154686#M54125 <P>Has anyone else seen full refresh snapshots trigger outside of their configured refresh window in Lakeflow Connect?</P><P>Here's our situation:</P><P>- We have a full refresh window configured to restrict snapshot operations to off-hours<BR />- On at least one occasion, a snapshot started outside of that window — during business hours<BR />- This caused unintended load on our SQL Server source during peak usage</P><P>The docs are clear that snapshots should only start during the next available time in the configured window, so this feels like unintended behavior. I'm still investigating whether there's a specific trigger (e.g. auto full refresh policy, a pipeline retry) that might bypass the window, but so far I haven't been able to pin down a consistent cause.</P><P>Has anyone else observed this? And if so, have you found any conditions that reliably cause a snapshot to ignore the configured window?</P><P>Would love to know if this is a known bug or if there's something in our configuration we should be looking at.</P> Wed, 15 Apr 2026 21:51:23 GMT https://community.databricks.com/t5/data-engineering/lakeflow-connect-sql-server-snapshots-firing-outside-configured/m-p/154686#M54125 lrm_data 2026-04-15T21:51:23Z https://community.databricks.com/t5/data-engineering/lakeflow-connect-sql-server-snapshots-firing-outside-configured/m-p/154786#M54143 <P><a href="https://community.databricks.com/t5/user/viewprofilepage/user-id/227217">@lrm_data</a>&nbsp;This is very unlike case for the refresh to be triggered outside the configured window. Though I would still suggest to check the Configured Window and Auto Full Refresh policy once to be sure.<BR />If still persists, then you may raise a support ticket for further resolution.</P> Fri, 17 Apr 2026 06:43:16 GMT https://community.databricks.com/t5/data-engineering/lakeflow-connect-sql-server-snapshots-firing-outside-configured/m-p/154786#M54143 Sumit_7 2026-04-17T06:43:16Z https://community.databricks.com/t5/data-engineering/lakeflow-connect-sql-server-snapshots-firing-outside-configured/m-p/154964#M54164 <P>Thank you ! I will continue monitoring and log internally if it continues happening.</P> Mon, 20 Apr 2026 15:00:57 GMT https://community.databricks.com/t5/data-engineering/lakeflow-connect-sql-server-snapshots-firing-outside-configured/m-p/154964#M54164 lrm_data 2026-04-20T15:00:57Z