- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2026 02:51 PM
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.
- Labels:
-
Delta Lake
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2026 11:43 PM
@lrm_data 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.
If still persists, then you may raise a support ticket for further resolution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2026 08:00 AM
Thank you ! I will continue monitoring and log internally if it continues happening.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2026 09:12 AM
Hello @Sumit_7 ,
I have tested a few scenarios and logged a ticket with Databricks and discovered the following:
Common Misconception
The start_window setting does not define a bounded time window during which full refreshes
are contained. It is simply a "no earlier than" anchor point.
What It Actually Means
Once the configured hour is reached, Lakeflow is permitted to begin an automatic full refresh
The refresh will run as long as it needs to — there is no end time or cutoff
A snapshot triggered at 9 PM can and will continue running well past that hour
What Else Can Trigger a Full Refresh (Outside the Window)
Even before the anchor time is reached, a full refresh can still be triggered by:
- A metadata change on a table
- A table truncation
- Manual triggers are also always allowed regardless of the window setting.
