Troubleshooting assistants
What each refusal from Senda means, what to do about it, and how to disconnect.
Most problems are the connection, not the question. Start here.
The assistant can't connect
- Check the server address is exactly
https://sendaship.com/api/mcp: nowww., no slash at the end. - If Senda says your plan doesn't include API access, nothing connects until it does. See the plan doesn't include API access below.
- After adding Senda, start a new chat (or restart the app) so the assistant loads its tools.
Refusals
When Senda refuses a connection, the assistant usually shows a code. Each one, what it means and what to do:
The connection has ended
unauthorized (401). It was disconnected, its sign-in expired and couldn't renew, the person who connected it left the company, or the API key was revoked. What to do: Connect Senda again in the assistant, or use a current API key.
The plan doesn't include API access
plan_required (403). Your company's plan doesn't include API access. What to do: Assistants and API keys come with the Operations or Enterprise plan. Compare plans, or change yours in Settings → Billing.
The key can't read records
scope_required (403). It is an EDI key, which can only exchange EDI files. What to do: Create an API key in Settings → Integrations and connect with that.
Too many requests
rate_limited (429). More than 120 requests in a minute on one connection or key. What to do: Wait a minute, then ask again.
Senda couldn't check the connection
service_unavailable (503). A brief problem on Senda's side. What to do: Try again in a minute.
When a tool can't answer
No such record
not_found. Senda has no such record in your company. What to do: Check the number. The assistant may have mixed up two ids.
The search was too broad
query_timeout. The search or page was too broad for Senda to answer. What to do: Ask with a more specific number or a few more words, or for a smaller page.
The request didn't fit the tool
invalid_arguments. The assistant asked in a way the tool doesn't accept, such as a page size over the limit. What to do: Ask again; the assistant usually corrects itself.
The connection can't read records
insufficient_scope. The connection lacks permission to read. What to do: Connect again by signing in, or with an API key.
Senda couldn't read the records
unavailable. A problem on Senda's side. The message carries an incident id. What to do: Try again shortly. If it keeps happening, contact us and quote the incident id.
An answer looks wrong
- Open the record from the link in the answer. Senda's page is the source; the assistant only reports what it read.
- A status or date that looks out of date is what your team last recorded in Senda. Update it there.
- An assistant can't open or summarise a document's file. Open it from the record's link.
Disconnect an assistant
To disconnect, an admin opens Settings → Integrations and, under Connected assistants, disconnects it. Access ends at once. You can also remove Senda in the assistant itself.
Anyone in your company can see the Connected assistants list. Disconnecting needs the Admin role. Even if your plan changes, anything already connected stays listed there so it can be disconnected.