> 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-receiver-trustline-missing.md).

# ESCROW\_RECEIVER\_TRUSTLINE\_MISSING

A role that receives escrow funds has no trustline for the escrow token.

`422 Validation Error` · request validation · v2 `deploy`, `update` and multi-release `manage-milestones`

### Example

```json
{
  "type": "https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/escrow-receiver-trustline-missing",
  "title": "Validation Error",
  "status": 422,
  "code": "ESCROW_RECEIVER_TRUSTLINE_MISSING",
  "detail": "Every role that can receive escrow funds must hold a trustline for the escrow token — roles.receiver (G…): no trustline for the escrow token.",
  "instance": "/escrow/single-release/v2/deploy",
  "traceId": "…",
  "extensions": {
    "trustline": "C…",
    "missing": [
      { "address": "G…", "roles": ["roles.receiver"], "reason": "trustline-missing" }
    ]
  }
}
```

### When it happens

Before building the transaction, the API checks that every address that can receive funds from the escrow can hold the escrow token. Roles that never receive funds (approvers, service providers, release signers, dispute resolvers, admin, observers) are not checked.

| Endpoint                          | Addresses checked                                                           |
| --------------------------------- | --------------------------------------------------------------------------- |
| Single-release `deploy`, `update` | `roles.receiver`, plus `roles.platform` when `platformFee > 0`              |
| Multi-release `deploy`            | every `milestones[].receiver`, plus `roles.platform` when `platformFee > 0` |
| Multi-release `update`            | `roles.platform` when `platformFee > 0`                                     |
| Multi-release `manage-milestones` | every `newMilestones[].receiver`                                            |

`extensions.missing` lists each failing address, the roles it plays, and a `reason`:

* `trustline-missing` — the account exists but has no trustline for the escrow token.
* `account-missing` — the account does not exist on this network.

### How to fix it

For `account-missing`, fund the account with XLM first. Then add a trustline to the escrow asset (for example USDC) on the same network, and retry.


---

# 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-receiver-trustline-missing.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.