---
title: Troubleshooting
description: The problems people actually hit, and what to do about each.
---

<span class="vy-eyebrow">Reference</span>

# Troubleshooting

## Rules

**I edited the document and the rule hasn't changed.**
Give it ten minutes — that's the checking cycle. After that: did you edit the
*same file*, or save a new one? A new file is a new document. Add it and tick
*replaces*. If the rule shows an orange note, Vythos can't read the file at
all — see [When a file can't be read](/using-vythos/unreadable-files).

**I uploaded the new version and nothing happened.**
Uploads update a rule when the file has the **same name** and is uploaded by
the **same person** who added the rule. A different name is a different
document.

**The rule's text is missing the part that matters.**
Open the rule and read what Vythos took from the document. Common causes: the
content is in an image; the PDF is a scan; the page has sub-pages in Notion
that are separate documents. See [File formats](/reference/file-formats).

**The rule has the wrong name.**
Names come from the document's first heading, or the file name. Give the
document a heading, or rename the file; the rule follows at the next check.

**Two rules say different things.**
That's a disagreement in your Playbook, and Vythos won't pick a winner — it
tells your tools the rules conflict. Retire the one that no longer applies.

**I can't add a rule.**
Only the workspace owner adds and retires rules today — the Playbook page is
theirs. Ask them to add the document, or to change the access you were given
so you're ready for when teammates can.

## Ask

**It says it doesn't have something I know is in there.**
Check the material is in memory — a file you never uploaded or synced isn't.
And check the asker's access: a category they can't see is never used in their
answer.

**It gave me an old figure.**
Look at which rule it cited and open the document. If the document is current
and the rule is behind, the rule updates within ten minutes. If the answer came
from a document rather than a rule, that document really does say that — worth
fixing at the source.

**It won't do the arithmetic.**
By design. Figures are quoted in the unit the rule states them in, never
combined into new ones, because a derived number appears in no version of your
Playbook. Ask gives you the figures and the rule.

**A follow-up was taken to mean something else.**
Ask reads a follow-up in light of the last few turns. If it guessed wrong, say
the subject — *"Greenleaf's logo"* rather than *"their logo"* — or start a
**New chat** for something unrelated.

**An answer I was waiting for isn't in the conversation.**
If you reloaded or left while it was being written, it's still finished and
kept — give it a few seconds and open the conversation again.

**Can I see what my team has asked?**
No, by design. Each person's conversations are theirs alone, like their memory
— the owner included. People ask more freely when their questions aren't read.

## Sources

**A file didn't sync.**
Check the format list. Legacy Office files, Apple iWork files, images and
scanned PDFs can't be read; they're reported with the reason rather than
skipped silently.

**Folder sync won't open a picker.**
Selecting a folder from your computer needs Chrome or Edge. Other browsers work
for everything else.

**I disconnected a source and the content is still searchable.**
Notion clears its memory on disconnect; Drive, GitHub and Gmail don't. Ask us
if you need a source's memory cleared on its own — deleting the workspace
removes everything.

## AI tools

**My tool connects but gets nothing useful.**
Check the access of whoever owns the key — a key carries that person's access.
Then check the tool is actually calling Vythos; some need to be told
explicitly ("get the rules from Vythos first").

**Every call is rejected.**
The key is wrong, revoked, or the header is missing `Bearer `. Create a new key
and paste it fresh.

**Claude Code connects and then drops.**
Use `--transport http`, not `sse`. The address ends in `/sse`, but the server
speaks Streamable HTTP.

**A draft check came back clean but the draft breaks a rule.**
Read the `unchecked` list in the result. Only banned words and payment terms
are checked today; a clean result means nothing was found among those. See
[Values](/concepts/values).

## Team

**My colleague never got their invitation.**
Invitations expire after 7 days — send another. Check spam. If email still
isn't arriving, tell us; we can get you the invitation link directly.

**A freelancer can see something they shouldn't.**
Check their access per category on the Members page, and their assigned
clients. Both take effect on their next question — there's nothing to re-issue.

**How do I remove someone?**
There's no way to remove a person in the app today. Set every kind of rule to
*No access* on their Members entry — it takes effect on their next question —
and ask us to close their account. See
[Your team and their access](/using-vythos/team-and-access).

**Someone left and rules stopped updating.**
Rules are read with the access of whoever added them. Add those documents again
from an account that's staying.

## Still stuck

Tell us what you did, what you expected, and what happened — with the rule's
name if it's about a rule. If it's about an AI tool, the tool's name and what
it called helps more than anything else.