Reference
Getting help
How to report a problem so it gets solved fast.
Before reaching out
- Check Troubleshooting — most connection, scope, and rerun problems resolve there.
- Reproduce once more and note what changed since it last worked.
What to include
A report with these five things gets solved fastest:
- Workspace: which workspace the problem is in.
- Run or proposal link: the exact run, proposal, or page — IDs beat descriptions. Quote record and run identifiers shown in the UI.
- Expected vs actual: what you expected, what happened instead, in one sentence each.
- Evidence: the relevant error text, validation message, or evidence chain — not a paraphrase of it.
- Recency: when it last worked, and what changed since (new source, edited mapping, new skill version).
While you wait
- Do not silently rerun structural failures; each unexplained rerun buries the evidence.
- Keep the workspace state intact — the run history and evidence links are what gets inspected.