> For the complete documentation index, see [llms.txt](https://help.enterprise.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.enterprise.ledger.com/help-center-v2/reference/error-codes.md).

# Error codes

The error codes that the Ledger Enterprise interface shows: what causes each one, what to do about it, and when to contact Ledger support.

This page explains each error code that the Ledger Enterprise interface can show. Each heading is the exact code. Search this page for the code that you see.

## Where you see a code

An error code names the cause of an error. It is written in capitals with underscores, for example `TOO_MANY_UTXOS`. One code is in lower case: `transaction_scan_escalated`.

The interface shows the code, with a copy action, in two places:

* On an error screen, and in the error step of a dialog.
* In the Operation history of a Request, under a failed Operation.

Some codes also show **Learn more**. It opens the entry for the code on this page, or a page with more detail.

The send form and the status of a failed Request do not show the code. The send form shows the message, sometimes with a link in it. The status of a failed Request shows the title of the message. Each entry below gives that message, so you can find the entry from the message.

The error report also contains the code. See [**Error reports for Support**](https://help.enterprise.ledger.com/help-center-v2/reference/statuses-and-errors.md#error-reports-for-support).

Almost every code that is not on this page shows a general message. To learn its cause, contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) with the error report. For an error on a Request, also give the Request ID.

## Send form

These codes stop a transfer in the send form. You cannot create the Request until you change the amount. Nothing moves.

On Ripple, the message shows under the amount. On Bitcoin, it shows beside the fee.

The message gives the figures that apply, shown here as *n*.

### AMOUNT\_BELOW\_DESTINATION\_ACTIVATION\_RESERVE

**Network:** Ripple.

**Message:** "This address is not activated on the XRP Ledger yet. Send at least *n* XRP to activate it."

**Cause:** The recipient address does not exist on the XRP Ledger yet. A payment to a new address must send at least the base reserve of the network.

**What to do:** Send at least the amount that the message gives. See [**Minimum balance**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/ripple.md#minimum-balance).

**Support:** Ledger support cannot change this amount. The network sets the base reserve.

### AMOUNT\_BELOW\_DUST

**Network:** Bitcoin.

**Message:** "This amount is too small to send. The network will not relay a payment below *n* sats."

**Cause:** The amount is below the smallest output that the network relays to this recipient. The minimum depends on the type of the recipient address.

**What to do:** Send at least the amount that the message gives.

**Support:** Ledger support cannot change this minimum. The network sets it.

### AMOUNT\_EXCEEDS\_BALANCE

**Network:** Bitcoin.

**Message:** "This amount is more than the *n* sats this Account holds."

**Cause:** The amount is more than the balance of the Account.

**What to do:** Send a smaller amount. The balance must cover the amount and the fee.

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if the message stays with an amount that the balance covers.

### BALANCE\_PARTLY\_UNECONOMIC

**Network:** Bitcoin.

**Message:** "Only *n* of *n* sats are spendable: the other coins cost more in fees than they hold. Retry when fees are lower."

**Cause:** Part of the balance is in unspent outputs that cost more in fees to spend than they hold. At the current fee rate, the platform does not spend them. The rest of the balance does not cover the amount.

**What to do:** Retry when network fees are lower. The **UTXOs** tab of the Account tags these outputs **Not worth spending**. See [**Unspent outputs**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#unspent-outputs).

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if the message stays when network fees are lower.

### NO\_FEE\_HEADROOM

**Network:** Bitcoin.

**Message:** "This amount leaves nothing for network fees, which cost at least *n* sats. Send a smaller amount."

**Cause:** The balance covers the amount, but not the amount and the network fees together.

**What to do:** Send a smaller amount.

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if the message stays with a smaller amount.

### NO\_SELECTION\_FOUND

**Network:** Bitcoin.

**Message:** "This Account's coins cannot be combined into this exact amount. Try a slightly different one."

**Cause:** The balance covers the amount and the fees. But every combination of unspent outputs leaves change that is too small to create.

**What to do:** Try a slightly different amount.

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if the message stays with several different amounts.

### SEND\_MAX\_LEAVES\_NOTHING\_TO\_SEND

**Network:** Bitcoin.

**Message:** "Network fees (*n* sats) would use up the *n* sats this Account can spend, leaving nothing to send."

**Cause:** **Send max** sends the whole spendable balance, minus the network fee. At the current fee rate, the fee uses all of it. Nothing is left above the minimum that the network relays.

**What to do:** Retry when network fees are lower.

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if the message stays when network fees are lower.

### CONSOLIDATION\_NOT\_WORTH\_FEES

**Network:** Bitcoin.

**Message:** "These coins would cost *n* sats in fees to merge, which leaves less than the *n*-sat minimum output. Retry when fees are lower."

**Cause:** You send from the Account to itself to consolidate its unspent outputs. At the current fee rate, the fees leave less than the minimum amount that an output needs.

**What to do:** Retry when network fees are lower. See [**Consolidating unspent outputs**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#consolidating-unspent-outputs).

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if the message stays when network fees are lower.

### TOO\_MANY\_UTXOS

**Network:** Bitcoin.

**Message:** "This Account holds too many UTXOs (*n*) to spend in one transaction, which is capped at *n*. Consolidate them first."

**Cause:** The Account holds more unspent outputs than one transaction can spend. Only **Send max** shows this code. It is the only send that spends every unspent output. The message gives the count and the maximum. See [**The 100 output limit**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#the-100-output-limit).

**What to do:** Consolidate the unspent outputs first. Then send again. See [**Consolidating unspent outputs**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#consolidating-unspent-outputs).

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if the consolidation also fails.

### TOO\_MANY\_INPUTS

**Network:** Bitcoin.

**Message:** "This amount needs *n* UTXOs, over the *n* limit. Send less, or consolidate UTXOs first."

**Cause:** To reach this amount, the transaction must spend more unspent outputs than the maximum. This happens when the balance is in many small outputs. See [**The 100 output limit**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#the-100-output-limit).

**What to do:** Send a smaller amount. Or consolidate the unspent outputs first. See [**Consolidating unspent outputs**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#consolidating-unspent-outputs).

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if the consolidation also fails.

## Failed Operations

These codes show in the Operation history of the Request, under a failed Operation. The history shows the title, the description, the code and **Copy error report**.

### BTC\_MEMPOOL\_CLUSTER\_LIMIT

**Message:** **Too many unconfirmed transactions**. "The network refused this transaction: it spends coins from unconfirmed incoming transactions linked to too many others. Nothing moved. Wait until they confirm before you send from this Account again."

**Cause:** The transaction spends outputs of incoming transactions that are not confirmed yet. It joins them in a **cluster** of unconfirmed transactions. Bitcoin Core refuses a cluster of more than 64 transactions or 101 kvB. The network error is `too-large-cluster`.

> **Note:** These limits are the Bitcoin Core defaults. They were checked against the [Bitcoin Core 31.0 release notes](https://bitcoincore.org/en/releases/31.0/) on 7 October 2026.

A common source is large incoming transactions that pay a low fee, such as deposit sweeps.

The Operation ends **Failed** (`FAILED`). Nothing moved.

**What to do:** Wait until the incoming transactions confirm. Then send from this Account again. Until they confirm, a new attempt can fail for the same reason.

To clear it sooner, ask the sender to raise the fee on the incoming transactions. Only the sender can replace them.

> **Warning:** Do not ask the sender to replace an incoming transaction that one of your pending transactions spends. Your pending transaction is then removed, and you must create it again.

To confirm the cause, and to prevent it, see [**If a transaction fails because of unconfirmed incoming transactions**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md#if-a-transaction-fails-because-of-unconfirmed-incoming-transactions).

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if the transaction fails again after the incoming transactions confirm. Give the Request ID, the error report, and the hash of each unconfirmed incoming transaction.

### transaction\_scan\_escalated

**Message:** **Transaction check escalated**. "The transaction check stopped this transaction."

**Cause:** Transaction Check screens the transaction once more, just before signature. This time, the result was worse than the result when the Request was created. The platform stopped the transaction. Nothing is signed or broadcast.

The Operation ends **Failed** (`FAILED`).

**What to do:** Open the **Transaction checks** section of the Request. Compare the **At creation** and **Pre-signature re-check** rows. Review the recipient before you create the transaction again. See [**Transaction Check**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/sending-assets.md#transaction-check).

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) with the error report if the **Transaction checks** section does not explain the result.

## Failed Requests

These codes show under the status of a failed Request, in the Request details. Only the title of the message shows.

### HSM\_ERROR

**Message:** **Approvals not verified**.

**Cause:** The platform could not verify the approvals of the Request. So it did not execute the Request. Nothing moved.

**What to do:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md). Give the Request ID.

**Support:** Always. Only Ledger support can find the cause.

### EXTERNAL\_SERVICE\_ERROR

**Message:** **Service error**.

**Cause:** A service that the platform relies on failed while it processed the Request. For example, a network service did not answer. Or Transaction Check could not complete when the platform created the Request. The failure can also happen while the platform sends the transaction for broadcast.

> **Warning:** This code can show after the transaction was broadcast. A new Request can then send the funds twice.

**What to do:** In the Request details, read the **On-chain status**. If it shows an Operation, the transaction was broadcast: do not create the Request again. If it shows **Not executed**, check the **Operations** tab of the Account for the transaction. On a Direct Access network, the Account has no **Operations** tab: check the Account address in a block explorer. Create the Request again only if the transaction is not there.

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) with the Request ID if the status is **Stuck**, or if you cannot tell whether the transaction was broadcast.

## Other screens

### ACCOUNT\_NOT\_FOUND

**Message:** **Account not found**. "This Account does not exist, or you do not have access to it." It shows in place of the content of the page, with **Retry**.

**Cause:** The Account does not exist in the Workspace, or you cannot see it. An Operator sees an Account only when its Rules name them, or when a Portfolio gives them access. See [**Which Accounts you can see**](https://help.enterprise.ledger.com/help-center-v2/guides/accounts/finding-accounts-and-balances.md#which-accounts-you-can-see).

**What to do:** Check the link or the Account ID. To get access, ask a Master Administrator to name you in the Rules of the Account. A Master Administrator can also add you to a Portfolio that holds it.

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) if you have access to the Account and the message stays after **Retry**.

### HEDERA\_ACTIVATION\_FAILED

**Message:** **Unable to activate the Hedera Account**. "Common causes: an invalid public key, insufficient funds, or a network delay. Check them before you retry." It shows in the activation dialog of a Hedera Account.

**Cause:** The platform could not complete the activation of the Account.

**What to do:** Check the three common causes that the message names: an invalid public key, insufficient funds, or a network delay. Then select **Retry**. See [**Activation before first use**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/hedera.md#activation-before-first-use).

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) with the error report if the activation still fails.

### USER\_REVOCATION\_BREAKS\_REVIEW\_RULE

**Message:** **Unable to revoke the Operator**. "A Rule on at least one active Account requires this Operator. To revoke them, first remove them from that Rule." The dialog also says "This Operator is now suspended."

**Cause:** Without this user, an approval step of a Rule would have fewer members than its required approvals. The platform refuses to create the revocation Request. In the interface, **Revoke** suspends the user first, so the user stays suspended.

**What to do:** First remove the user from that Rule, or from the group that the step names. The step must keep at least as many members as its required approvals. So lower the required approvals, or add another member. Then revoke the user again. See [**When the platform refuses a revocation**](https://help.enterprise.ledger.com/help-center-v2/administration/users.md#when-the-platform-refuses-a-revocation).

To lift the suspension instead, select **Restore access** on the user's page.

**Support:** Contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) with the error report if you cannot find the step that holds the user.

## Related

* [**Statuses and errors**](https://help.enterprise.ledger.com/help-center-v2/reference/statuses-and-errors.md)
* [**Contacting Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md)
* [**Bitcoin (BTC)**](https://help.enterprise.ledger.com/help-center-v2/reference/networks/bitcoin.md)


---

# 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://help.enterprise.ledger.com/help-center-v2/reference/error-codes.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.
