Semantic Health Warnings
What the Semantic Health issue list means — uncertified reveals, missing node descriptions, orphan reveals, pending corrections — and how to clear them
Your Semantic Health score is below the green band and the issue list shows error, warning, or info rows you want to clear.
Symptoms
- The score card reads amber (60–79) or red (below 60) instead of green (80+).
- Rows tagged
error,warning, orinfo, for example "8 reveals (67%) are not certified" or "Node 'orders' has no description". - The page shows "Loading semantic health…" and never resolves.
- "No issues found" but the score is still below 100.
- There's no Recompute button in the header.
Causes & fixes
Work the list by severity — error (red) first, then warning (amber), then info (grey). Each row's fix line points you to the exact place to act.
| Symptom | Cause | Fix |
|---|---|---|
Many error/warning rows about uncertified reveals | A large share of your reveals are not certified — the heaviest score penalty | Certify them in Forge; uncertified reveals carry the largest drag and lower Orion's confidence. |
warning: a node has no description | The node is missing a description | Open Forge → that node and add a description (−2 per node). |
info: reveals not used by any dashboard | Orphan reveals — defined but unpinned | Pin them to a Mosaic or archive unused metrics. |
info: no drill paths defined | The model has nodes but no drill paths | Add a path in Drill Paths. |
warning: corrections pending review | Orion corrections haven't been applied or dismissed | Review and apply them in Quality → Corrections. |
| Page shows "Loading semantic health…" forever | The request to fetch health data failed | Reload the page; if it persists, confirm the workspace has a connected warehouse and modelled nodes. |
| Score looks stale after you fixed issues | The score reflects the state at load time | Reload the tab, or have a Luminary click Recompute. |
| "No issues found" but score below 100 | Not all penalties surface as separate rows for every object | Check the Overview and Context Health summary; certifying reveals and adding node descriptions are the highest-impact wins. |
| No Recompute button | You are not a Luminary — Recompute is Luminary-only | Ask a workspace admin to recompute after your fixes; the score still loads automatically. |
Still stuck?
Make a batch of fixes, then have a Luminary click Recompute once to see the combined effect — recomputing after every edit is slow and unnecessary. Don't confuse this tab with Data health, a separate Luminary-only audit in Lumen that checks structural problems (duplicate nodes, misconfigured domains) and does not produce a 0–100 score.