> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/escrow/escrow-string-too-long.md).

# ESCROW\_STRING\_TOO\_LONG

A String field exceeded its on-chain maximum length.

`422 Validation Error` · escrow contract error · multi-release v2, single-release v2

### Example

```json
{
  "type": "https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/escrow-string-too-long",
  "title": "Validation Error",
  "status": 422,
  "code": "ESCROW_STRING_TOO_LONG",
  "detail": "A String field exceeded its on-chain maximum length (engagement_id 100, title 100, description 500, milestone status 50, evidence 500, dispute reason 500).",
  "instance": "/…",
  "traceId": "…"
}
```

### When it happens

Simulation of the transaction fails on-chain with this contract error: a text field is longer than the contract allows. The on-chain limits are engagement\_id 100, title 100, description 500, milestone status 50, evidence 500, dispute reason 500.

### How to fix it

Shorten the offending field to within its limit, then rebuild and resubmit.


---

# 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://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/escrow/escrow-string-too-long.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.