# Errors and recovery

Source: https://docs.getdeeprecall.com/reference/errors/

> Respond to access, validation, missing-resource, rate-limit, and processing failures.

Use the error category and operation status to decide what to do next. Do not turn an uncertain response into a success claim.

| Category               | Meaning                                        | Next step                                                  |
| ---------------------- | ---------------------------------------------- | ---------------------------------------------------------- |
| Unauthorized           | Missing, expired, or invalid authentication    | Reconnect through the supported sign-in flow               |
| Forbidden              | Access or scope does not permit this operation | Review the requested permissions and account access        |
| Not found              | Resource unavailable to this account           | Check the ID and owning account                            |
| Invalid request        | Input or source violates the contract          | Correct the fields, format, or size before retrying        |
| Rate limited           | Too many requests                              | Back off; honor retry guidance if provided                 |
| Upstream/model failure | Processing or generation could not complete    | Check status; retry deliberately after a confirmed failure |
| Internal error         | The service could not complete the operation   | Keep safe diagnostic context and contact support           |

A missing resource and a resource owned by someone else may produce the same not-found response. Do not infer another person’s data from the error.

## MCP errors

An MCP tool failure is marked as an error result. Read the sanitized message and keep it separate from a successful payload. Never assume a tool ran successfully because the client displayed a tool call.

## Writes need special care

If a write acknowledgement was lost, its result is unknown. Check status through supported account tooling or recall later before resubmitting. A queued save is processing, not a failure.

Document retries are available when a stored original can be processed again. Parser errors such as an image-only PDF require a supported source, not endless retries.

## Ask for help

Provide the operation, approximate time, provider/client, visible error, and a job ID if one was returned. Keep passwords, tokens, OAuth secrets, access-bearing URLs, and private source content out of the report. Use [Contact](/help/contact/) when you need help with an account-specific issue.