Starting a Diagnosis
- Give an answer a thumbs-down in Ask Anything.
- In the feedback form, select the reasons that describe what went wrong (for example a logic error or a missing filter) and optionally add a note.
- Click Send and suggest fix.
What the Diagnosis Investigates
The diagnosis agent re-reads the conversation up to the answer you rated and inspects your Context Layer — the metrics, entities, and definitions the answer relied on. It checks whether those components exist and whether their definitions are correct, so it can tell a fixable modeling problem apart from a one-off reasoning error. The investigation is read-only. It looks at your Context Layer but never changes it — any fix is applied separately, through the Builder, only if you choose to.What You Get Back
A diagnosis ends in one of three ways:- A fix to apply. The diagnosis explains what went wrong and recommends a change to your Context Layer. Click Fix now to jump into the Context Builder with the suggested fix pre-loaded, or Dismiss to leave things as they are.
- Nothing to fix. The answer matched your Context Layer, so there’s no definition to change — the failure was a one-off. Your feedback is still recorded.
- Couldn’t finish. If the investigation errors out, your feedback is saved and you can Try again.
Applying the Fix
Fix now doesn’t change anything on its own — it opens the Builder pre-loaded with the suggested correction so you can review it, then release it through your draft and deploy. See Context Layer Versioning for how changes are released. This works for versioned components — entities, metrics, segments, and entity dimensions — which are the components the Builder edits. It does not cover features or feature dimensions, which are managed live rather than through the Builder.If a diagnosis recommends a change to a feature or a feature dimension, there’s no Fix now handoff for it — apply the change manually on the feature’s page.