Celiq
v0.12Open app โ†—
Docs/Troubleshooting/Refresh Issues

Refresh Issues

Cached results, a query that timed out, and how to rerun every tile โ€” plus how live tiles differ from a saved query state

TracerWeaverLuminaryUpdated June 2026 ยท 4 min read
โœฆ
In this section
Part of Celiq's semantic layer platform. Connect your warehouse, model your data once, query it everywhere.
๐Ÿ“
Note

Results aren't refreshing the way you expect โ€” you see cached numbers, a query that timed out, or you're unsure when data re-runs.

Symptoms

  • A Cached badge shows in the Discover action bar.
  • An error reads "Query timed out".
  • A Mosaic tile didn't refresh after a data load.
  • You're unsure whether a tile shows live data or a snapshot.

Causes & fixes

SymptomCauseFix
Cached badge in DiscoverResults came from cache rather than a fresh warehouse runClick Run to re-execute against the warehouse.
"Query timed out"The result set is too large or the query too heavyLower the row limit (100 / 500 / 1,000 / 5,000 / 10,000) or add filters, then re-run. Filter before raising the limit โ€” a higher limit doesn't reduce work.
A Mosaic tile didn't refresh after a big data loadTiles re-run on open, on Rerun all tiles, or when the global date/frame/comparison/filters changeUse โ‹ฏ โ†’ Rerun all tiles (or press R) to refresh every tile and regenerate the Orion briefing.
Comparison silently turned off after a refreshThe comparison query failed (no resolvable date range) and Celiq fell back to the simple querySet an explicit global date range, then re-run.
A pinned Prism tile shows different numbers from yesterdayPrisms and tiles are live โ€” they save the question, not the answer, and re-run against current data on openThis is expected; there is no "last refreshed" snapshot to manage.

Live vs snapshot

Celiq tiles and Prisms are live: they store the query, not a frozen result, and re-execute against your warehouse every time they open. Mosaic tiles do not snapshot data โ€” each one re-runs its own query on open, on Rerun all tiles, or whenever the global date, frame, comparison, or filters change.

Still stuck?

If a query keeps timing out even after lowering the limit and filtering, the warehouse may be slow or unreachable โ€” check the connection in the Admin Console / Warehouses. If a tile errors instead of timing out, confirm it has a valid domain and reveal, and run Data health.