When a user's AI assistant can't finish something in TaskRay, it tells the user why, and that message is often what reaches you. Every error names one of eight kinds, and the kind tells you who can fix it. When Salesforce itself refused the request, the error also repeats Salesforce's own message, which is usually the text a user pastes.
Who Fixes Which Error
| The error says | What it means | Who fixes it |
|---|---|---|
validation |
The request was refused as it stood, for example by one of your validation rules, or because it changes an active template. | The assistant corrects the request and tries again. |
auth |
Salesforce no longer accepts the user's connection, because the session expired, the sign-in was revoked or the org can't be reached. | The user, by signing in again at mcp.taskray.com/oauth/login. |
permission |
The user's Salesforce permissions don't allow the action. | You, if the user should be able to do it. Review their permission sets and sharing access. |
not_found |
The record doesn't exist, or the user can't see it. | The assistant checks the record exists. If it does, review the user's sharing access. |
conflict |
The record changed after the assistant read it, a unique value is already in use, or another process had the record locked. | The assistant reads the record again or retries. The user doesn't need to sign in again. |
governor |
Your org has reached a Salesforce API limit. | Time. Try again later. |
feature |
Your org's TaskRay edition or add-ons don't include the capability, such as template export or import without TaskRay Premium or the Template Migration add-on. | Retrying won't help. The message says what the org needs. |
internal |
Something unexpected went wrong, on the TaskRay MCP server or in Salesforce, or Salesforce took too long to answer. | The assistant tries again. If a change might already have been saved, it checks the record first. If it keeps happening, contact TaskRay Support. |
Good to Know
- Deletes, bulk changes and a few other high-impact changes wait for the user to approve them. If an assistant reported a change that hasn't shown up in TaskRay, it's most likely still waiting, as described in TaskRay MCP Tool Reference: Approvals for Delete, Bulk and Elevated Tools.
- A request a tool doesn't accept, such as a filter the tool doesn't have, is refused with a short note naming the detail at fault, rather than partly ignored. A tool that isn't in the user's tool list doesn't answer at all, as described in TaskRay MCP Tool Reference: Overview.
Frequently Asked Questions
Q. A user's assistant was refused by one of our validation rules. Is that expected?
Great question! Yes. Your validation rules apply to an assistant's changes the same way they apply to the user's own edits. The error carries the rule's message from Salesforce, and the assistant can correct the request and try again.
Where to Go Next
- TaskRay MCP Tool Reference: What Assistants Can Find and Change Safely: the checks that protect your team's work, and the custom fields you manage.
- TaskRay MCP Tool Reference: Approvals for Delete, Bulk and Elevated Tools: which changes wait for the user to approve them.
Have a question this reference doesn't answer? Not to worry, our Support Team is ready to help! Contact TaskRay Support with what the user asked their assistant to do, the exact error text, and whether the org is production or sandbox.