> 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/statuses-and-errors.md).

# Statuses and errors

Every Request status and Operation status on Ledger Enterprise, the error messages, and Workspace maintenance: what each means, and what to do about it.

## Request statuses

A Request has one status at a time. The API returns a state. The interface shows a label, and the label depends on where you look:

* The Requests list and the Request details use one set of labels.
* The **Request status** filter on the Requests list uses another set. Three of its labels differ from the list and details labels.

Both sets and the API state are given here.

<table><thead><tr><th width="160">List and details label</th><th width="110">Filter label</th><th width="164.05078125">API state</th><th width="320">Meaning</th><th>Reached the blockchain?</th></tr></thead><tbody><tr><td><strong>Initiating…</strong></td><td><strong>Initiating</strong></td><td><code>INITIAL</code></td><td>Created, and still being prepared for review</td><td>No</td></tr><tr><td><strong>To review</strong> or <strong>Awaiting approval</strong></td><td><strong>Awaiting approval</strong></td><td><code>PENDING_APPROVAL</code></td><td>Collecting approvals. The only status where approve and reject are possible. <strong>To review</strong> means you can approve it now</td><td>No</td></tr><tr><td><strong>Executing…</strong></td><td><strong>Executing</strong></td><td><code>EXECUTING</code></td><td>Fully approved, and being carried out</td><td>In progress</td></tr><tr><td><strong>Completed</strong></td><td><strong>Completed</strong></td><td><code>EXECUTED</code></td><td>Complete. For a transaction, the operation was broadcast</td><td>Broadcast</td></tr><tr><td><strong>Rejected</strong></td><td><strong>Rejected</strong></td><td><code>ABORTED</code></td><td>An Approver rejected it, or the Creator declined on the Ledger device while creating it</td><td>No</td></tr><tr><td><strong>Blocked</strong></td><td><strong>Blocked</strong></td><td><code>BLOCKED</code></td><td>Another Request canceled it. See <a href="#blocked">Blocked</a></td><td>No</td></tr><tr><td><strong>Expired</strong></td><td><strong>Expired</strong></td><td><code>EXPIRED</code></td><td>It reached its expiry before full approval</td><td>No</td></tr><tr><td><strong>Failed</strong></td><td><strong>Failed</strong></td><td><code>FAILED</code></td><td>Execution was attempted and did not succeed</td><td>Usually no. A failure during broadcast can leave the transaction broadcast. See <a href="https://help.enterprise.ledger.com/help-center-v2/reference/error-codes.md#external_service_error"><code>EXTERNAL_SERVICE_ERROR</code></a></td></tr><tr><td><strong>Stuck</strong></td><td><strong>Stuck</strong></td><td><code>STUCK</code></td><td>The platform could not finish the cleanup after a failure, a rejection, an expiry or a block. Contact Support with the Request ID</td><td>Unclear</td></tr></tbody></table>

In the list, the **Approvals** column does not show **To review** or **Awaiting approval**. For a pending Request, it shows the approvals granted against those required, and the time to expiry. The Request details show the label, with a count such as "2 of 3 approved".

For the state values in an API response, see the [**API documentation**](https://help.enterprise.ledger.com/api-documentation-v2).

Over the API, the approval challenge of a new Request is not ready while the Request is `INITIAL`. If you are an Approver of its current step, `GET /requests/{id}/challenge` then returns HTTP status `425` with a `Retry-After` header. Wait the number of seconds that the header gives, then send the call again.

> **Important:** Only **Executing…** (`EXECUTING`) and **Completed** (`EXECUTED`) mean anything has reached the blockchain. The one exception is a **Failed** (`FAILED`) Request that failed during broadcast. See [`EXTERNAL_SERVICE_ERROR`](https://help.enterprise.ledger.com/help-center-v2/reference/error-codes.md#external_service_error). A pending Request has not moved value, however long it has been there.

The platform signs a transaction only while its Request is **Executing…** (`EXECUTING`). It refuses to sign for a Request in any other status.

**Completed means broadcast, not confirmed.** The network decides when an operation confirms. The **On-chain status** of the Request shows the Operation status. See [**Reviewing operation history**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/operation-history.md).

A pending Request past its expiry shows as **Expired**. Its **Review** and **Reject** buttons disappear. The API state changes to `EXPIRED` up to one hour later.

During Workspace maintenance, the platform does not expire Requests. See [Requests during maintenance](#requests-during-maintenance).

### How the status filter works

The **Request status** filter on the Requests list offers all nine statuses as separate options, with the filter labels above. Select one or more of them. A Request appears when its API state matches one of your selections.

The filter reads the API state. So for up to one hour after its expiry, a Request still matches **Awaiting approval** and not **Expired**.

### Blocked

Only a Request that is not fully approved can be blocked. A **Revoke user** Request blocks others. As soon as it is created, it blocks every Request that the user being revoked created. It also blocks every pending Request that this user approved at an earlier step.

The blocked Request is canceled and cannot be approved. A Revoke user Request blocks these Requests even if it is later rejected.

Nothing moved. Create the operation again if it is still needed.

## Operation statuses

A Request that sends a transaction creates an Operation. The Operation has its own status, which follows the transaction on the network. The interface shows a label, and the API returns a status.

The status badge shows the label in the **On-chain status** column of the Requests list, and in the Request details. The **Operation status** filter and the Operation history in the Request details use the same labels, with two differences:

* `SUBMITTED` reads **Confirming** on the badge, and **Submitted** in the filter and the Operation history.
* The filter has no **Replaced** option. A replaced Operation matches **Dropped**.

<table><thead><tr><th width="145.88671875">Label</th><th width="157.7421875">API status</th><th>Meaning</th></tr></thead><tbody><tr><td><strong>Queued</strong></td><td><code>SCHEDULED</code></td><td>Accepted by the broadcast system but not submitted to the network</td></tr><tr><td><strong>Confirming</strong> on the status badge. <strong>Submitted</strong> in the filter and the Operation history</td><td><code>SUBMITTED</code></td><td>Submitted to the network, and waiting for chain inclusion</td></tr><tr><td><strong>Confirming</strong></td><td><code>ON_CHAIN</code></td><td>Included on-chain and waiting for the required confirmation threshold</td></tr><tr><td><strong>Confirmed</strong></td><td><code>CONFIRMED</code></td><td>The required confirmation threshold was reached</td></tr><tr><td><strong>Dropped</strong></td><td><code>DROPPED</code></td><td>No longer progressing on-chain</td></tr><tr><td><strong>Replaced</strong></td><td><code>DROPPED</code></td><td>Replaced by another transaction, for example after a speed-up or a cancellation</td></tr><tr><td><strong>Failed</strong></td><td><code>FAILED</code></td><td>Failed before submission to the network</td></tr><tr><td><strong>Failed on-chain</strong></td><td><code>FAILED_ON_CHAIN</code></td><td>Failed after submission to the network</td></tr><tr><td><strong>Unknown</strong></td><td><code>UNKNOWN</code></td><td>The status is inconsistent and needs investigation</td></tr></tbody></table>

A replaced Operation and a dropped Operation have the same API status. The interface shows **Replaced** when a replacement transaction took its place.

On a network where Ledger Enterprise does not track transactions, `SUBMITTED` is the final status. The badge reads **Submitted**, and its tooltip tells you to check the transaction in a block explorer.

### When an Operation fails

The Operation history shows the reason under the failed Operation: a title and a description of the cause, the error code, and **Copy error report**. Some codes also show **Learn more**. The status of the Operation in the Request details also shows the title.

[**Error codes**](https://help.enterprise.ledger.com/help-center-v2/reference/error-codes.md) gives the cause of each code that has its own message, and what to do. Any other failure shows the status label, with "Reason unavailable."

The interface does not show the network's own error. To get it, send the Request ID to Support.

* **Failed**: the network did not accept the transaction. Nothing moved. You can create the transaction again. If it fails again, contact Support before a third attempt. On Bitcoin, 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).
* **Failed on-chain**: the network received the transaction and rejected it. The network can charge a fee. Find the transaction hash in a block explorer to see the network's reason.
* **Unknown**: do not create the transaction again until Support confirms its status. A second transaction can send the funds twice.

## Why an action is unavailable

| What you see                                                                                                                                                                                                                                               | Reason                                                                                                                                                                        |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| A section missing from the navigation                                                                                                                                                                                                                      | Your role does not give access to it, or it is not enabled for your Workspace                                                                                                 |
| A greyed-out action with the tooltip "You do not have permission to send". For other operations, the tooltip shows stake, delegate, unstake, undelegate, sign-message, interact-with-contract or deploy-contract in place of send                          | No Rule on the Account lets you create that operation. A Master Administrator must add you to the first step of a Rule                                                        |
| A greyed-out action with the tooltip "This Account does not have enough available balance."                                                                                                                                                                | The available balance of the Account is zero. Message signing is not affected                                                                                                 |
| A greyed-out action with the tooltip "A Request to edit this Account is already in progress."                                                                                                                                                              | A Request to edit the Account is pending. Wait until it is reviewed, rejected or expired                                                                                      |
| A greyed-out **Edit** with the tooltip "A Request to edit it is already in progress."                                                                                                                                                                      | Another edit Request for this Account is pending                                                                                                                              |
| A greyed-out **Edit** with the tooltip "A transaction Request on this Account is already in progress."                                                                                                                                                     | Transactions from the Account are not complete yet. Wait for them to finish                                                                                                   |
| A Hedera Account with an **Inactive** badge in the Accounts list. Its **Send** is greyed out with the tooltip "You cannot send from an inactive Hedera Account." Its **Edit** is greyed out with the tooltip "You cannot edit an inactive Hedera Account." | The Account is not activated. An Administrator activates it from the Account page                                                                                             |
| No **Review** on a pending Request                                                                                                                                                                                                                         | You are not an Approver in the current approval step, or you reviewed already                                                                                                 |
| No **Reject** on a pending Request                                                                                                                                                                                                                         | You are not an Approver in the current step or in an earlier step                                                                                                             |
| Rules that cannot be edited on an Account                                                                                                                                                                                                                  | The Account uses a shared Policy. A Master Administrator can edit the Policy. A Master Administrator can also edit the Account and select **Manual** to give it its own Rules |
| In the send form, the banner "No Send Rule on this Account matches this transaction." and a greyed-out **Review** with the tooltip "No matching Rule found for the given amount and recipient"                                                             | No Rule lets you send that amount to that recipient. Check the amount thresholds and the Whitelists of the Rules                                                              |
| **Anonymized** in place of an Approver's name                                                                                                                                                                                                              | Only Administrators see the names of other users. Other users see only their own name                                                                                         |
| A banner that starts with your Workspace name and "is in read-only maintenance", and every change fails                                                                                                                                                    | Ledger has put the Workspace in read-only maintenance. See [Workspace maintenance](#workspace-maintenance)                                                                    |

## Messages and error screens

These messages stop a sign-in, a device step or a Request in the interface. The tables give the title of each message.

A message that shows an error code is on [**Error codes**](https://help.enterprise.ledger.com/help-center-v2/reference/error-codes.md), under that code.

### Sign-in and device messages

A Personal Security Device (PSD) user can get these messages at sign-in, during pairing for single sign-on (SSO), or during registration. **Ledger device locked**, **No Ledger device selected** and **Update required on your Ledger device** can also show at any other device step.

| Title                                     | Cause                                                                                                                          | What to do                                                                                                                                                                                                                                                                |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Ledger device not recognized**          | The platform finds no Workspace where this Ledger device belongs to a user                                                     | Contact an Administrator of your Workspace                                                                                                                                                                                                                                |
| **Sign-in interrupted**                   | The sign-in was declined or canceled on the Ledger device                                                                      | Select **Retry**, then confirm the sign-in on the device                                                                                                                                                                                                                  |
| **Ledger device locked**                  | The Ledger device is locked                                                                                                    | Unlock the device, then select **Retry**                                                                                                                                                                                                                                  |
| **No Ledger device selected**             | The browser prompt that lists devices closed with no device selected                                                           | Connect and unlock the device. Select **Retry**. Then select the device in the browser prompt                                                                                                                                                                             |
| **Update required on your Ledger device** | The Ledger Vault app is missing, or its version is not the version that the platform requires                                  | Select **Start update**. When the update is complete, select **Retry**. See [Your device](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/your-device.md)                                                                                        |
| **PSD does not match your SSO session**   | During SSO pairing, your identity provider sends a device ID that is not the device ID of the Ledger device that you connected | Contact your IT service. See [**The device ID in the IdP**](https://help.enterprise.ledger.com/help-center-v2/administration/users/single-sign-on.md#the-device-id-in-the-idp)                                                                                            |
| **PSD already linked to another user**    | During SSO pairing, your SSO identity or this PSD user is already paired                                                       | Contact your IT service                                                                                                                                                                                                                                                   |
| **Device paired with another workspace**  | During registration, the Ledger device has a pairing record for another Workspace                                              | Reinstall the Ledger Vault app on the device, then select **Retry**. If the problem continues, contact Ledger support. See [Your device](https://help.enterprise.ledger.com/help-center-v2/start-here/get-started/your-device.md#your-device-and-the-workspace-partition) |

### Request messages

| Title                                                                       | Cause                                                                                                                                                       | What to do                                                                                                                                                                                                             |
| --------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Request approval interrupted**                                            | You declined the Request on the Ledger device during **Review**. No rejection is sent, and the Request stays pending                                        | Select **Retry** to review it again. To stop the Request, select **Reject**. See [Declining on the Ledger device](https://help.enterprise.ledger.com/help-center-v2/guides/requests.md#declining-on-the-ledger-device) |
| **Approval canceled**                                                       | You declined on the Ledger device while you created the Request. The platform rejected the new Request                                                      | Select **Create Request again** to create a new Request with the same details                                                                                                                                          |
| **Unable to cancel the Request**                                            | You declined on the device while you created the Request, and the platform could not confirm that it canceled the Request. The Request can still be pending | Select **Cancel and create again**. The interface cancels the first Request, then creates a new one                                                                                                                    |
| **Unable to reject the Request**                                            | The platform did not accept your rejection. The Request is not rejected                                                                                     | Select **Retry** to send the rejection again                                                                                                                                                                           |
| **Unable to confirm the rejection**                                         | The platform accepted your rejection, but the Request does not show **Rejected** yet                                                                        | Select **Check again** to read the status again. It does not send a second rejection                                                                                                                                   |
| **Request creation failed**                                                 | The new Request reached a status other than pending before your approval, or it expired before a retried approval                                           | Find the Request in **Requests** and read its status. Create the operation again if it is still needed                                                                                                                 |
| **Risk detected**, **Threat detected** or **Transaction Check unavailable** | Transaction Check flagged an EVM transaction, or the check could not complete                                                                               | Select **Approve anyway** to continue to your Ledger device, or **Cancel** to stop. See [Transaction Check results](https://help.enterprise.ledger.com/help-center-v2/guides/requests.md#transaction-check-results)    |
| **Unable to replace the transaction**                                       | You selected **Speed up** or **Cancel transaction**, and the transaction ended before its network hash became available                                     | Return to **Requests** and read the status of the Request                                                                                                                                                              |
| **No permission to sign**                                                   | A dapp asked for a message signature, and no Rule on the Account lets you sign messages                                                                     | Ask a Master Administrator to add you to the first step of a Rule for message signing                                                                                                                                  |
| **No permission to execute**                                                | A dapp asked for a contract interaction, and no Rule on the Account lets you interact with contracts                                                        | Ask a Master Administrator to add you to the first step of a Rule for contract interaction                                                                                                                             |

### Error reports for Support

Most error screens have a **Copy error report** button. On some screens, it is an icon with the tooltip **Copy error report**. It copies a technical report of the error, in JSON format.

When you contact [**Ledger support**](https://help.enterprise.ledger.com/help-center-v2/contacting-support.md) about an error, paste this report into your support request. For an error on a Request, also give the Request ID.

The report contains:

* the error and its technical cause;
* the error code, when the error has one;
* the address of the page that showed the error;
* the user agent of your browser;
* your user details;
* the date and time of the report.

These screens have no **Copy error report**: **Ledger device locked**, **No Ledger device selected**, **Request approval interrupted**, **Approval canceled** and **Unable to replace the transaction**.

## Workspace maintenance

Ledger can put a Workspace in maintenance. Ledger sets the maintenance mode and ends it. No user of the Workspace can change it. There are two modes.

### Full maintenance

The Workspace is closed. Every page of the interface opens the maintenance page instead. Its title is your Workspace name, followed by **is under maintenance**. **Retry** reloads the page. The maintenance page stays until maintenance ends.

Over the API, every call fails with HTTP status `503` and the message "Workspace is in maintenance mode. Please try again later."

### Read-only maintenance

A banner shows at the top of every page: "*Workspace name* is in read-only maintenance. You can view Workspace data, but you cannot make changes or use the Ledger device until it ends."

You can read Workspace data, and you can sign out. The platform refuses every change. That includes creating, approving and rejecting Requests. Over the API, a read works, and a change fails with HTTP status `403`.

### Requests during maintenance

These rules apply in both modes:

* Nobody can approve or reject a Request.
* A fully approved Request does not progress. It continues after maintenance ends.
* The platform does not expire Requests. A Request that reaches its expiry keeps the API state `PENDING_APPROVAL`. It expires after maintenance ends.

In the interface, a pending Request still shows **Expired** when it reaches its expiry.

## Related

* [**How governance works**](https://help.enterprise.ledger.com/help-center-v2/concepts/how-governance-works.md)
* [**Requests and approvals**](https://help.enterprise.ledger.com/help-center-v2/guides/requests.md)
* [**Reviewing operation history**](https://help.enterprise.ledger.com/help-center-v2/guides/transactions/operation-history.md)
* [**Error codes**](https://help.enterprise.ledger.com/help-center-v2/reference/error-codes.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/statuses-and-errors.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.
