Skip to main content

Running a Dashboard

Opening a dashboard runs the query behind each tile and renders the results. The numbers you see always reflect the latest execution, not a stored snapshot.

How tiles execute​

Each tile runs its own query against the connection it uses. Tiles render as soon as their data arrives, so a dashboard fills in tile-by-tile rather than waiting for everything at once.

Background execution for heavy tiles​

Some queries take longer to run. To keep the dashboard responsive, tiles can execute in the background: the page stays interactive while the slow tile finishes and then updates in place. This means one expensive query won't block the rest of the report.

Refreshing​

Re-open or refresh the dashboard to re-run its tiles and pull current data. For unattended updates, point a tile at a query that is also scheduled, so the data is recomputed on a timetable.

Tiles with inputs​

If a tile's query uses form variables, the dashboard can prompt for those values, letting viewers filter the report themselves.

Tips​

  • Keep chart tiles backed by aggregated queries — they run faster and read better.
  • Use background execution for any tile whose query scans a lot of data.
  • Watch the group logs if a tile is consistently slow or failing.