> 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-signer-must-be-approver-and-release-signer.md).

# ESCROW\_SIGNER\_MUST\_BE\_APPROVER\_AND\_RELEASE\_SIGNER

approve\_and\_release\_milestones requires the signer to be in BOTH roles.approvers and roles.release\_signers.

`403 Forbidden` · escrow contract error · multi-release v2, single-release v2

### Example

```json
{
  "type": "https://docs.trustlesswork.com/trustless-work/v2-en/api-rest/errors/escrow-signer-must-be-approver-and-release-signer",
  "title": "Forbidden",
  "status": 403,
  "code": "ESCROW_SIGNER_MUST_BE_APPROVER_AND_RELEASE_SIGNER",
  "detail": "approve_and_release_milestones requires the signer to be in BOTH roles.approvers and roles.release_signers.",
  "instance": "/…",
  "traceId": "…"
}
```

### When it happens

Simulation of the transaction fails on-chain with this contract error: the combined `approve_and_release_milestones` action requires one wallet that holds both roles. It is raised when the signing wallet is in only one of `roles.approvers` or `roles.release_signers`.

### How to fix it

Sign with a wallet listed in both `roles.approvers` and `roles.release_signers`, or run the approve and release steps separately with their respective signers.


---

# 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-signer-must-be-approver-and-release-signer.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.