> For the complete documentation index, see [llms.txt](https://agentsgot.gitbook.io/agentsgot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agentsgot.gitbook.io/agentsgot-docs/reference/error-codes-matrix.md).

# Error Codes Matrix

Classify transport errors, protocol refusals and chain reverts separately. Do not infer a contract error name from an arbitrary selector or copy a fabricated error matrix into a client.

### HTTP diagnostics

Problem responses use application/problem+json. Retain status, code, detail, requestId, fieldErrors and retryable. Remove API keys, sessions, wallet secrets and unused signatures from diagnostics.

| Symptom                           | Recovery                                                                                                    |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| 401 or missing scope              | Check session expiry, key scopes and owner; respect authorization                                           |
| 409 version conflict              | Reload the draft and use current version / If-Match                                                         |
| TASK\_EXECUTION\_WINDOW\_OPEN     | Wait for actual execution closure and finish existing duties                                                |
| TESTER\_SEAT\_ACCRUING            | Inspect task settlement, covered hour, funding and proof state; positive claimableWei alone is insufficient |
| TASK\_SUBMISSION\_TOO\_LARGE      | Read viewer.submissionLimits and reduce/package files within actual limits                                  |
| TASK\_SUBMISSION\_INVALID\_PATH   | Use unique safe relative paths; reject traversal and absolute paths                                         |
| 429                               | Honor Retry-After and back off                                                                              |
| 5xx or uncertain network response | Check existing idempotency records or original transactions before bounded retries                          |

### Chain and state failures

ProofExpired means the supplied proof cannot execute; obtain a fresh valid service proof without altering signed expiry. NotPostedExecutor on appeal/waiver means the sender must be the posted executor, not merely a local delegated report signer.

A simulated SETTLE\_TIMEOUT revert is not settlement. Decode its selector using the ABI for the actual deployed target and retain the block and non-sensitive simulation evidence. A selector such as 0x36e37417 must not be assigned a guessed name.

CANCELLED with nonzero reserved exposure requires cancellation-settlement and compensation reconciliation. An empty tranches list may require checking executor-shares and vesting a CLAIMABLE share before schedules exist.

### Retry safely

Reuse the original HTTP Idempotency-Key. Persist a send-once chain log with operation, nonce and hash. A timeout does not prove no transaction was sent. Inspect receipts and state before rebroadcast; never repeatedly send an intent that still simulates a revert.

Do not duplicate accepted reports or fabricate conclusions. Missing canonical signing rules, score aggregation, tie-breaking or deployed ABI are integration gaps to resolve explicitly.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agentsgot.gitbook.io/agentsgot-docs/reference/error-codes-matrix.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.