[connections] document configurable connection freshness (#24474)

## Summary & Motivation

As title

Internal-RevId: be78fb47b0999cc0382f3ba9b730a2c7b637d931

Author: maximearmstrong

docs/docs/guides/labs/connections/bigquery.md

@@ -161,6 +161,8 @@ Use filtering to control which projects, datasets, tables, and views are synced.
 
 ## Connection freshness
 
+import ConnectionFreshnessCadence from '@site/docs/partials/\_ConnectionFreshnessCadence.md';
+
 Once a BigQuery Connection is created, Dagster automatically tracks changes to your BigQuery tables and emits a materialization on the corresponding Connection asset each time the underlying table is updated in BigQuery. As a result, your Connection assets reflect the most recent state of the BigQuery tables without needing to define a sensor or schedule.
 
 ### Prerequisites
@@ -174,6 +176,10 @@ The roles granted in [Grant required permissions](#step-12-grant-required-permis
 
 Tables must live in a region included in [`region_qualifiers`](#optional-configure-region-qualifiers) (defaults to `region-us` and `region-eu`); changes in regions not listed there will not be detected.
 
+### Configuring the cadence
+
+<ConnectionFreshnessCadence />
+
 ### Triggering downstream assets
 
 Each detected change produces a standard Dagster materialization event on the Connection asset, so code-defined assets can depend on a Connection asset like any other upstream. Combine that with an [Automation Condition](/guides/automate/declarative-automation) to materialize a downstream asset whenever its BigQuery parent changes:

docs/docs/guides/labs/connections/databricks.md

@@ -145,6 +145,8 @@ Use filtering to control which catalogs, schemas, tables, views, and notebooks a
 
 ## Connection freshness
 
+import ConnectionFreshnessCadence from '@site/docs/partials/\_ConnectionFreshnessCadence.md';
+
 When the Databricks Connection has a SQL warehouse configured, Dagster automatically tracks changes to your Unity Catalog tables and emits a materialization on the corresponding Connection asset each time the underlying table is updated in Databricks. As a result, your Connection assets reflect the most recent state of the Databricks tables without needing to define a sensor or schedule.
 
 ### Prerequisites
@@ -156,6 +158,10 @@ Connection freshness for Databricks shares the same configuration as lineage tra
 
 If no warehouse is configured, freshness signals are not emitted.
 
+### Configuring the cadence
+
+<ConnectionFreshnessCadence />
+
 ### Triggering downstream assets
 
 Each detected change produces a standard Dagster materialization event on the Connection asset, so code-defined assets can depend on a Connection asset like any other upstream. Combine that with an [Automation Condition](/guides/automate/declarative-automation) to materialize a downstream asset whenever its Databricks parent changes:

docs/docs/guides/labs/connections/snowflake.md

@@ -128,6 +128,8 @@ Use filtering to control which databases, schemas, and tables are synced. Patter
 
 ## Connection freshness
 
+import ConnectionFreshnessCadence from '@site/docs/partials/\_ConnectionFreshnessCadence.md';
+
 Once a Snowflake Connection is created, Dagster automatically tracks changes to your Snowflake tables and emits a materialization on the corresponding Connection asset each time the underlying table is updated in Snowflake. As a result, your Connection assets reflect the most recent state of the Snowflake tables without needing to define a sensor or schedule.
 
 ### Prerequisites
@@ -136,6 +138,10 @@ Connection freshness for Snowflake reuses the warehouse, role, and credentials a
 
 The privileges granted in [Step 1.1: Create role and user to use with Dagster Connections](#step-11-create-role-and-user-to-use-with-dagster-connections) (`USAGE` on databases and schemas, `REFERENCES` on tables and views) are sufficient for the role to see rows in `INFORMATION_SCHEMA.TABLES` for the objects it has access to.
 
+### Configuring the cadence
+
+<ConnectionFreshnessCadence />
+
 ### Triggering downstream assets
 
 Each detected change produces a standard Dagster materialization event on the Connection asset, so code-defined assets can depend on a Connection asset like any other upstream. Combine that with an [Automation Condition](/guides/automate/declarative-automation) to materialize a downstream asset whenever its Snowflake parent changes:

docs/docs/partials/_ConnectionFreshnessCadence.md

@@ -0,0 +1,10 @@
+By default, Dagster polls the source for changes every minute. You can change the cadence in the **Freshness** tab of the connection editor.
+
+Available presets:
+
+- **Every minute** (default)
+- **Every 5 minutes**
+- **Every 15 minutes**
+- **Custom cron** — any standard 5-field cron string (e.g. `0 */2 * * *`)
+
+A timezone selector accompanies the cron, which is useful when you pick a less frequent schedule (for example, "every day at 2 AM in America/New_York"). Slower cadences reduce queries against your source at the cost of longer worst-case detection lag.