Skip to content

Refresh

Platform (dbtCharts.com)

This page describes dbt Charts Platform, the hosted product at dbtCharts.com. These features are not part of the open source dct engine.

A dashboard's charts run queries against your database. Refresh policy decides when those queries actually re-run, versus when a viewer sees a cached result.

What's Platform-owned

Refresh in Platform is manual: a dashboard re-runs its queries when someone asks it to. There is no scheduled refresh (no cadence, timezone, event trigger, retry or notification settings), and none of that is configurable anywhere in the product today.

Who can trigger a refresh follows the same path-based access model as viewing and editing: refreshing is one of the capabilities a role can carry, so whoever holds an Editor-level (or custom) grant with that capability at a path can refresh it. Anyone holding it sees a manual refresh control in the dashboard's own toolbar. Like access, that binding is Platform state keyed to a dashboard's path, not something in your project's YAML or git history.

The manual refresh button among the dashboard's other toolbar actions

What core gives you

Running dbt Charts on its own (dct serve or dct render), you control freshness directly through the query-result cache. By default the cache is a file in your user cache directory, so results outlive the server process and a restart does not refresh anything; a result is reused until it is older than its query's cache: duration. Pass --no-cache to re-run every query on every request, or point --cache <path> (or DCT_CACHE_PATH) at a file of your own. See the dct serve reference for the full set of caching flags.

Platform builds on these same primitives; a manual refresh is what decides when to invalidate and re-run, not a different query or storage mechanism underneath.