Data health
Workspace-wide audit of your semantic layer for common configuration issues.
Why use it: Surface duplicate nodes, unused reveals, and misconfigured domains before they cause query errors.
Where to find it: Lumen → Data health
Who can use it: Luminary (workspace admin) only.
Data health
Celiq monitors your semantic layer for common issues and surfaces them in Lumen.
Where to find it: Lumen → Data healthWhat it checks
Duplicate node names
Two nodes with the same name in different projects. When Orion runs a query, it uses the domain's project to pick the right one — but duplicates are worth reviewing.
How to fix: Go to Forge, identify which node belongs to which project, rename or delete the duplicate.Unused reveals
A reveal with zero mosaics and zero scenes using it. Not broken — just potentially outdated.
How to fix: Delete it if it's no longer needed, or add it to a mosaic if it should be used.Domains without project
A domain with no project set. When Orion resolves nodes for this domain, it falls back to the connection's project. This works but can cause issues in multi-project setups.
How to fix: Forge → Domains → edit the domain → assign a project.Node / domain project mismatch
A node's project doesn't match its domain's project. Queries may resolve to the wrong schema.
How to fix: Check which project each node and domain should belong to, and update accordingly.Why it matters
These issues don't cause immediate failures but they cause confusing errors later. A duplicate node that resolves to the wrong one gives wrong query results with no error message. Data health surfaces these before they cause problems.