Knowledge Graph Missing Relationships
Joins, owners, or relationships don't show up in Orion's answers — define them in the model and the Business Knowledge Graph so the context resolves
Orion's answers are missing the connections you expect — an owner, an experiment, an OKR — or joins between entities don't appear.
Symptoms
- Orion answers a bare metric ("CAC increased by 18% last week") with no owner, experiment, or OKR context.
- People, experiments, or objectives you expected aren't reflected in answers.
- A relationship between two entities isn't being used.
Causes & fixes
The Business Knowledge Graph is additive — Orion still answers data questions accurately from your semantic layer without it. Missing relationships mean the graph is empty or incomplete, not broken.
| Symptom | Cause | Fix |
|---|---|---|
| Orion gives a metric movement with no "who / why / so what" | The knowledge graph is empty | Add entities in Suite → AI Analysts → Knowledge Graph (/knowledge) — People, Experiments, and OKRs are the highest-value starting points. |
| A metric isn't attributed to an owner | No People entry links that person to the metric they own | Add the team member and the metric they own, so Orion can say "CAC is owned by Ravi (Marketing)". |
| A metric movement isn't tied to a cause | The relevant Experiment (A/B test, campaign, initiative) isn't logged | Log the experiment with name, description, start/end date, owner, and outcome so Orion can connect movements to it. |
| Movements lack strategic context | No OKRs are recorded for the quarter | Add objectives and key results by quarter so Orion frames movements against targets. |
| You're unsure the context is being used | You can't see what context Orion receives | Open the Context Preview tab to verify exactly what context Orion would get for a given question. |
Still stuck?
If you mean joins between data nodes (not business entities) — for example an orders node that should join to customers — those are defined in the semantic model in Forge, not in the knowledge graph. Confirm the join exists in the node/domain definition so it resolves in queries and drilling. Adding and editing the knowledge graph requires the Weaver or Luminary role.