> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/start-here/ai-agents/mcp-reference/errors-and-recovery-behavior.md).

# Errors and recovery behavior

JSON-RPC, authentication, authorization, validation, plan, conflict, and retry behavior.

## Error layers

| Layer                             | Meaning                                                         | Recovery                                                  |
| --------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------- |
| HTTP 401                          | Missing, expired, revoked, or wrong-resource credential.        | Follow the authentication challenge and reconnect.        |
| HTTP 403 or insufficient scope    | The grant lacks a required scope.                               | Reauthorize with the minimum required scope.              |
| JSON-RPC parse or request error   | The envelope is malformed.                                      | Correct the protocol request.                             |
| Invalid parameters                | Arguments do not match the schema or allowed combination.       | Correct the named field and retry as a new request.       |
| Not found                         | The ID is absent or outside the tenant and permission boundary. | Verify account and ID. Do not probe other IDs.            |
| Forbidden                         | The user lacks resource-level permission.                       | Obtain permission from the account or organization owner. |
| Plan limit reached                | The plan or allowance blocks the action.                        | Wait for reset, reduce work, or review `/upgrade`.        |
| Confirmation required or rejected | Preview is missing, stale, changed, or already used.            | Request and review a new preview.                         |
| Operation in progress             | The same work or cancellation is active.                        | Monitor the existing operation.                           |

## Retry policy

Retry temporary transport and rate-limit failures only when the operation contract allows it. Keep the same idempotency key for an identical uncertain mutation. Follow `Retry-After` where present.

Do not retry validation, permission, plan, terminal operation, or changed-confirmation errors as if they were transient.

## Ambiguous external delivery

An operation can know that a delivery was committed without knowing the final external receipt. Preserve the operation ID and do not send a duplicate automatically.

## Support data

Record the client and version, tenant-safe account identifier, tool name, target ID, operation or upload ID, timestamp, and sanitized error code. Never send bearer tokens, refresh tokens, signed upload URLs, passwords, or private feed URLs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/documentation/start-here/ai-agents/mcp-reference/errors-and-recovery-behavior.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.