Reveal Not Loading
Discover or a tile won't load a reveal — "No reveals yet", "No nodes found for this reveal", warehouse connection errors, and missing tables
In this section
Part of Celiq's semantic layer platform. Connect your warehouse, model your data once, query it everywhere.
Note
You opened Discover (or a Mosaic tile) and the reveal won't load — either there's nothing to pick, the reveal is empty, or the warehouse can't be reached.
Symptoms
- The FieldPanel shows "No reveals yet".
- You see "No nodes found for this reveal".
- An error like "Cannot reach data warehouse" or "Table or dataset not found".
- A tile shows "This tile references fields that no longer exist in the node schema" or Table not found.
Causes & fixes
| Symptom | Cause | Fix |
|---|---|---|
| FieldPanel shows "No reveals yet" | No reveal has been authored in any domain | Create a reveal in Forge — the prompt links there. |
| "No nodes found for this reveal" | The reveal's primary node and joins aren't defined | Check the domain definition in Forge so the primary node and joins resolve. |
| "Cannot reach data warehouse" | The warehouse connection is down or misconfigured | Check the connection in the Admin Console / Warehouses. |
| "Table or dataset not found" | The node's physical table, or the connection's project/dataset, is wrong | Verify the node's physical_table and the connection's project/dataset. |
| "BigQuery location mismatch" | The connection region differs from the dataset region | Set the connection's location to match the dataset. |
| Tile: "This tile references fields that no longer exist in the node schema" | The reveal's node changed and a selected field was removed or renamed | Open the tile's embedded Discover editor and re-pick the fields. |
| Tile shows Table not found | The source table is missing from the warehouse | Check the node's table in Forge and your warehouse connection. |
| Prism: No connection found. Add a connection in Admin → Connections. | Celiq couldn't resolve a warehouse connection for the Prism's domain | Add or fix the domain's connection under Admin → Connections, then re-run. |
| Prism: Connection credentials are not configured. Re-enter them in Admin → Connections. | The resolved connection is missing credentials or service-account JSON | Re-enter the connection credentials, then re-run. |
Still stuck?
If a reveal loads but returns no rows or a service-account error, that is an access problem rather than a loading one — see Permission Denied. For warehouse-wide health checks, run Data health, which flags duplicate nodes and misconfigured domains. Building reveals, nodes, and connections requires the Weaver or Luminary role — ask a workspace admin if you can't reach Forge.