Troubleshooting start here
The canonical version always lives at https://tavina.ai/docs/support/troubleshooting/start-here
Troubleshooting start here
Use this page when Tavina is not doing what the customer expected. Keep troubleshooting customer-safe: do not ask for passwords, private keys, one-time codes, payment card numbers, or unnecessary sensitive files.
Start with the symptom
Ask what the customer was trying to do and which area was involved:
- sign-in or account access;
- notifications not arriving on a phone or computer;
- ordinary chat;
- file upload or Knowledge Library Source processing;
- long-document answer, citation, or coverage problem;
- connected app;
- Settings or memory;
- billing, subscription, or privacy request.
Collect the exact visible error message or processing state.
Common first checks
1. Confirm the customer is signed in to the expected account.
2. Ask them to refresh Tavina and try the smallest reproducible step.
3. Check whether the problem is tied to one conversation, one file, one Source, one Catalog, or one connected app.
4. Ask whether Tavina reported a processing state such as partial, failed, OCR-needed, encrypted/blocked, or pending.
5. Ask whether a connected app needs a higher trust level or reconnection.
6. If the answer involved a long Source, ask whether Tavina used targeted retrieval or whole-Source traversal.
Known error guidance
| Customer symptom | Safe first guidance |
| — | — |
| Upload says failed, partial, OCR-needed, or encrypted/blocked | Explain that Tavina may not have full document access. Try a text/Markdown export, an unencrypted file, or a clearer scan. |
| Answer has no citations | Ask whether Tavina answered from chat context, selected chunks, or a Source with citation metadata. Ask it to cite the Source if available. |
| Whole-document summary seems incomplete | Ask Tavina to report coverage: processed, skipped, failed, and still pending sections. |
| Connected app action fails | Check connection status, trust level, app permissions, and whether the action is supported. |
| Tavina remembers something wrong | Have the customer correct Tavina and review available memory/settings controls. |
| Billing, deletion, formal privacy, or legal policy question | Do not guess. Route to the current approved support/privacy/billing path. |
When to escalate
Escalate when:
- the same issue reproduces after basic checks;
- a file or Source shows a state that the customer cannot resolve;
- Tavina claims full-document coverage but cannot show coverage details;
- connected-app behavior could have changed external data unexpectedly;
- the customer asks for account deletion, formal privacy commitments, refund terms, or legal/billing policy;
- the issue involves possible data exposure or unsafe action.