Documentation › Dashboards
Caching and refreshing data
How Embiro BI caches chart data for an hour, how to force a refresh, set auto-refresh, and change cache timeouts.
To keep dashboards fast and avoid querying your database every time someone opens them, Embiro BI keeps chart results for a while. This is called caching.
How it works
- When a chart runs, its result is kept for one hour.
- Anyone who opens the same chart with the same filters within that hour gets the saved result instantly, without a query to your database.
- The chart's corner shows when the data was fetched, such as Fetched 12 minutes ago.
- After an hour, the next viewer's visit runs the query again.
This matters most for Google Sheets and busy databases: a dashboard opened 200 times an hour reads the source once per chart and filter combination, not 200 times.
Get the latest data now
- One chart: its menu (⋮) → Force refresh.
- The whole dashboard: ⋯ → Refresh dashboard.
Both re-run the queries and save the new results for everyone.
Auto-refresh
For dashboards left open, such as on a TV: ⋯ → Set auto-refresh interval → every 10 seconds up to every 24 hours. Choose something sensible: refreshing every minute re-queries your database every minute. To make it the dashboard's default for everyone, set it in edit mode and save.
Change how long results are kept
From the most specific to the most general, the first one set wins:
- Chart: ⋯ → Edit chart properties → Cache timeout (in seconds).
- Dataset: Edit Dataset → Settings → Cache timeout.
- Database connection: Advanced → Performance → Chart cache timeout.
- Otherwise one hour (3600 seconds).
Use a shorter timeout (such as 300 seconds) for data that changes during the day, and a longer one (such as 86400, a day) for monthly figures. Set -1 to never cache.
Alerts and reports
Scheduled reports and alerts always run fresh queries, so emails show current numbers.
Something unclear or missing? Tell us and we'll improve this page.