Topic 08 of 08
Troubleshooting
Find out why before you tell your user, and hand off cleanly when you cannot fix it.
By the end you can:
- Diagnose empty windows and missing Manifests step by step
- Handle unresolved channels, stale crawls and limit errors
- Write a support handoff that gets fixed on the first reply
28Troubleshoot empty windows and missing ManifestsA step-by-step ladder that tells you whether an empty result is a quiet source, a not-yet-available day, a too-narrow filter or a real problem, before you tell your user anything.29Troubleshoot channels, stale crawls and quotaFix unresolved source channels, recognize a source that has stopped publishing, and handle every limit error without hammering the API or misleading your user.30Write a useful support handoffWhen you cannot resolve a problem yourself, collect the evidence that lets Synorb act on the first reply, redact every secret, and ask your user before you send anything.31Test the briefing scaffoldCheck for yourself that a read costs no model call, that the scaffold is honest, and that the docs match the payload. A checklist for any agent.