---
url: /errors/no_target_allocation_for_mandate.md
---
# `NO_TARGET_ALLOCATION_FOR_MANDATE`

## Description

The mandate has no target allocation. A delegation must rebalance the compartment to the target allocation of the mandate, so the delegation cannot occur.

## HTTP Status

`422 Unprocessable Entity`

## `doc_url` Format

`<docs-base-url>/errors/no_target_allocation_for_mandate`

## Typical Causes

* The discretionary manager has not set a target allocation for the mandate.
* The request uses the wrong mandate.

## Example

Request: `PUT /v1/investment/compartments/{compartmentId}/delegation`

Response:

```json
{
  "errors": [
    {
      "code": "NO_TARGET_ALLOCATION_FOR_MANDATE",
      "message": "Mandate '5d7f9b1d-3e5f-4a7b-8c0d-2e4f6a8b0c1e' has no target allocation",
      "doc_url": "https://docs.example.com/errors/no_target_allocation_for_mandate"
    }
  ]
}
```

## How To Fix

1. Make sure that the mandate ID is correct.
2. Ask the discretionary manager to set a target allocation for the mandate.
3. Send the delegation request again.

## Transfer Conversion

This code can also occur during asynchronous transfer completion into an empty
compartment under mandate. The worker logs the error. It is not an HTTP error
from `POST /v1/investment/transfers`.

The apply transaction rolls back. The transfer stays `RECORDED`, both position
projections stay unchanged, and no conversion switch is stored. The job ends
with a domain failure. It does not retry automatically.

After the manager sets an allocation, an operator must redrive the completion
job. A duplicate incoming event alone does not redrive the job because the
inbox already contains that event.