docs(auto-run): document scheduled column re-runs as distinct from Auto-run

[george-dilthey]

What changed

Added a new section "Scheduled column re-runs ('Re-run columns on a schedule')" to docs/auto-run.md, inserted between the "Column-level auto-run" and "Conditional runs" sections. The section explains that scheduled column re-runs are a distinct table-level feature from Auto-run, can run even when table-level Auto-run is OFF (because scheduled runs use forceRun=true and bypass the master switch), links to the existing scheduled-columns.md for full setup details, and documents the "Scheduled to run: [frequency]" indicator visible in column settings.

Why

Intercom conversation 215475117348337 (Megan Fogarty, Lucid Software, Enterprise plan): columns set to auto-run were not firing when new rows were added. Her table had individual column auto-run ON but table-level Auto-run OFF — visible in screenshots attached to the ticket. The Run Settings panel shows both "Auto-run" (greyed out/OFF) and "Re-run columns on a schedule" (ON) as separate toggles, causing confusion about their relationship.

The support team (Bo, then Ariana) correctly explained that table-level Auto-run is the master switch — but Fin could not resolve the ticket because auto-run.md never mentions "Re-run columns on a schedule" as a distinct feature in the same panel, and never explains that scheduled re-runs work independently of the Auto-run master switch.

The auto-run.md doc thoroughly covers the master switch hierarchy (verified via code: action-field.ts:3807, record.service.ts:3149). A separate scheduled-columns.md doc covers the scheduled re-run feature in full. The missing piece was a bridge section in auto-run.md explaining how the two coexist and that scheduled runs bypass the Auto-run gate (forceRunTableJob.ts:55–57, forceRun=true).

Source link(s)

• Intercom conversation: https://app.intercom.com/a/inbox/_/inbox/conversation/215475117348337
• Slack thread (linked from ticket): https://clay-hq.slack.com/archives/C0A6U0B1XAR/p1784226332945079
• Code evidence (verifier PASS):
  • Table-level master switch: clay-base/apps/api/v3/tables/services/record.service.ts:3149 and clay-base/apps/api/v3/tables/services/action-field.ts:3807
  • Scheduled runs bypass the gate: clay-base/apps/api/v3/tables/domain/runner/scheduled-table-runs/forceRunTableJob.ts:55–57 (forceRun=true)
  • Plan availability: clay-base/libs/shared/src/billing/plan.ts:114,143 (ScheduledTablesLimit: 100 for Trial and all paid plans)

Uncertainties

The "Re-run columns on a schedule" UI is additionally gated by an Eppo feature flag (scheduled-runs / EppoFeatureFlags.EnabledScheduledRuns) whose current rollout scope is not visible in the code repo. The ScheduledTablesLimit flag is set to 100 for all paid plans (Trial through Enterprise), and an Enterprise customer confirmed seeing the feature in their UI (screenshots in the Intercom conversation). No Slack discussions about rollout limitations were found. No beta framing added, consistent with the paid-plan evidence. If the Eppo flag is narrower than "all paid plans," a beta note may be needed.

Related observations

conditional-runs.md and credit-usage.md already reference scheduled-columns.md and "Re-run columns on a schedule" by name, confirming this is a concept already in the documentation ecosystem. No other doc updates needed for consistency.

Closes DOC-1240

[linear-code]

DOC-1240