Refresh interval and data availability

When you configure a refresh interval for a virtual table—such as every 15 minutes—note that this setting defines the intended frequency for initiating a refresh, not a guaranteed time for data availability.

The configured refresh interval indicates the earliest time a new refresh cycle can begin. Actual data availability in your Databricks workspace depends on the successful completion of the entire virtual table refresh process, which includes internal coordination and execution steps managed by CONNECT data services.

Expectations for refresh intervals:

• A virtual table with a 1-hour refresh interval operates on an approximate schedule. It does not guarantee data availability exactly at the end of the interval.

• Refreshed data may become available 10 to 20 minutes after the configured interval.

• This behavior is expected and aligns with the CONNECT data services architecture, which prioritizes reliability, scalability, and consistent data delivery over strict real-time guarantees.

When designing solutions, treat virtual table refresh intervals as planning guidelines rather than strict service-level agreements for data arrival. Design downstream analytics, dashboards, and automated workloads in Databricks to accommodate slight variations in data availability.

This approach enables CONNECT data services to reliably manage virtual table refreshes across tenants and platforms, ensuring scalable and consistent data access.