Help

Troubleshooting

The five failures that account for nearly every support mail, and what each one means.

The connector fails, or every call returns 401

The OAuth grant was revoked or expired. Remove the connector in the client and add it again; approval happens in the browser. For agent tokens, a 401 means the token was revoked or has expired, and the fix is a new one.

Answers feel stale

The assistant reads whatever the last sync indexed, and the extension does the syncing. Open the Syla extension and press sync; new material is answerable within minutes of indexing.

A tool is missing from tools/list

The connection's scopes exclude it, which is working as designed. Assistants request the standard set; agent tokens carry only the scopes picked at minting, so a token made for scheduling will not show view_page.

Lost an agent token

It cannot be recovered, only replaced: Syla stores a hash, not the token. Mint a new one in Connections and revoke the old.

Rate limited

Back off and honour Retry-After. Sustained polling is the usual cause; whats_changed and changes_since exist precisely so an agent can ask “what moved” instead of re-reading everything on a timer.

Still stuck

founder@usesyla.app. Include the client (ChatGPT, Claude, your own agent) and what the failing call returned.