Skip to content

Data Ingestion¶

The Warehouses and AI Services pages are built from a copy of your Snowflake usage data, stored inside your account and refreshed on a schedule. The Data Ingestion page shows the status of those refreshes and lets you run one manually.

What you get¶

Next scheduled run¶

A live countdown to the next automatic refresh, or a one-click way to turn scheduling on if it's off.

Current status¶

Whether a refresh is running right now, and the error if the last one failed.

Run now¶

Pull the latest numbers on demand instead of waiting for the next scheduled run.

Run history¶

The last 30 refreshes: when each one ran, whether it succeeded, how long it took, and the date window it covered.

How it stays current¶

A refresh runs automatically once a day. The first refresh happens the moment you install the app, pulling 30 days of history so the rest of the app has something to show right away; every refresh after that is incremental, pulling only what's changed since the last run. If scheduling is ever off, a banner at the top offers a one-click Set up auto-refresh.

Running it yourself¶

Click Run now any time you want the latest figures without waiting. The Backfill dropdown next to it controls how far back that one run reaches:

  • Incremental (default): the fast, normal option. Continues from the last successful run.
  • Last 7 / 30 / 90 / 180 days: forces a full re-pull of that many days, overwriting whatever was there. Use this if you suspect a gap, or want deeper history than the automatic 30-day backfill gave you.

Only one refresh runs at a time; Run now is disabled while one is already in progress.

Reading the run history¶

Each row is one refresh: when it started, its status, how long it took, and the date window it covered. Export CSV downloads the full history, including what triggered each run (the initial install pull, a scheduled run, or a manual Run now) and how many rows it pulled, not just the 30 rows on screen.

Good to know¶

A failed run doesn't lose data: everything from the last successful run stays exactly as it was until the next refresh succeeds. The current-status banner only appears for states that need your attention (running, or failed with the error message); a normal successful refresh shows nothing there, since the run history and the rest of the app's numbers already speak for themselves.