Has anyone else seen full refresh snapshots trigger outside of their configured refresh window in Lakeflow Connect?
Here's our situation:
- We have a full refresh window configured to restrict snapshot operations to off-hours
- On at least one occasion, a snapshot started outside of that window — during business hours
- This caused unintended load on our SQL Server source during peak usage
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.
Has anyone else observed this? And if so, have you found any conditions that reliably cause a snapshot to ignore the configured window?
Would love to know if this is a known bug or if there's something in our configuration we should be looking at.
