> 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 failure reason on Ledger Enterprise, what each means, and what to do about it.

## Request statuses

A Request has one status at a time. The interface shows a label; the API returns a state. They are not the same word, so both are given here.

<table><thead><tr><th width="99.94140625">Label</th><th width="164.05078125">API state</th><th width="349.2421875">Meaning</th><th>Reached the blockchain?</th></tr></thead><tbody><tr><td>Initial</td><td><code>INITIAL</code></td><td>Created, and still being prepared for review</td><td>No</td></tr><tr><td>Pending</td><td><code>PENDING_APPROVAL</code></td><td>Collecting approvals. The only status where approve and reject are possible</td><td>No</td></tr><tr><td>Executing</td><td><code>EXECUTING</code></td><td>Fully approved, and being carried out</td><td>In progress</td></tr><tr><td>Executed</td><td><code>EXECUTED</code></td><td>Complete. An on-chain operation has been broadcast</td><td>Broadcast</td></tr><tr><td>Rejected</td><td><code>ABORTED</code></td><td>An Approver rejected it</td><td>No</td></tr><tr><td>Blocked</td><td><code>BLOCKED</code></td><td>Another approved Request invalidated this one</td><td>No</td></tr><tr><td>Expired</td><td><code>EXPIRED</code></td><td>It reached its expiry before full approval</td><td>No</td></tr><tr><td>Failed</td><td><code>FAILED</code></td><td>Execution was attempted and did not succeed</td><td>No</td></tr><tr><td>Stuck</td><td><code>STUCK</code></td><td>Execution stalled and needs attention</td><td>Unclear</td></tr></tbody></table>

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

> **Important:** Only Executing and Executed mean anything has reached the blockchain. A Request in Pending has not moved value, however long it has been there.

**Executed means broadcast, not confirmed.** The network decides when an operation confirms. See [**Reviewing operation history**](/help-center-v2/guides/transactions/operation-history.md).

A pending Request past its expiry shows as Expired. Its approve and reject actions disappear.

### How the status filter groups them

The filter offers four options, not nine. Each covers several states.

<table><thead><tr><th width="172.69140625">Filter option</th><th>States it covers</th></tr></thead><tbody><tr><td>Pending</td><td>Initial, Pending</td></tr><tr><td>Approved</td><td>Executing, Executed</td></tr><tr><td>Rejected</td><td>Rejected</td></tr><tr><td>Failed</td><td>Blocked, Expired, Failed, Stuck</td></tr></tbody></table>

This is why filtering on Failed also returns expired and blocked Requests.

### Blocked

A Request is blocked when a different Request is approved that invalidates it. The blocked Request is canceled and cannot be approved.

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

## Operation failure reasons

<table><thead><tr><th width="181.02734375">Reason</th><th>What happened</th><th>What to do</th></tr></thead><tbody><tr><td>Failed to broadcast</td><td>The transaction could not be published to the network</td><td>Nothing moved. Retry. If it repeats, contact support</td></tr><tr><td>Missing funds</td><td>Available balance was too low when execution was attempted</td><td>Check Available rather than Total. Fund the Account or reduce the amount</td></tr><tr><td>Max fee too low</td><td>The network required a higher fee than the authorized maximum</td><td>Create the transaction again with a faster fee strategy</td></tr><tr><td>Amount too low</td><td>The amount was below what the network accepts</td><td>Increase the amount</td></tr><tr><td>On-chain error</td><td>The network rejected the transaction</td><td>Check a block explorer for the network's own reason</td></tr><tr><td>Internal error</td><td>The signing infrastructure returned an error</td><td>Nothing moved. Contact support with the operation hash</td></tr></tbody></table>

## Why an action is unavailable

<table><thead><tr><th width="357.890625">What you see</th><th>Likely reason</th></tr></thead><tbody><tr><td>A section missing from the navigation</td><td>Not available to your role, or not enabled for your Workspace</td></tr><tr><td>An Account visible but not actionable</td><td>You are not a permitted Creator for that operation on that Account</td></tr><tr><td>An action greyed out on an Account</td><td>The Account is suspended, or a Request on it is still pending</td></tr><tr><td>No approve or reject on a pending Request</td><td>You are not in the current approval step, or you have already acted</td></tr><tr><td>An Account that cannot be edited</td><td>It has unresolved Requests. Wait for them to complete, expire, or be rejected</td></tr><tr><td>Rules that cannot be edited on an Account</td><td>It adopts a shared Policy. Edit the Policy instead</td></tr><tr><td>Amount rejected as outside every Rule</td><td>No Rule authorizes that amount for you</td></tr><tr><td><strong>Anonymized</strong> in place of an Approver's name</td><td>Operators see their own name only. Administrators see every name</td></tr><tr><td>Staking section saying to contact an Administrator</td><td>Staking Rules are not enabled on the Account</td></tr></tbody></table>

## Related

* [**How governance works**](/help-center-v2/concepts/how-governance-works.md)
* [**Requests and approvals**](/help-center-v2/guides/requests.md)
* [**Reviewing operation history**](/help-center-v2/guides/transactions/operation-history.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.enterprise.ledger.com/help-center-v2/reference/statuses-and-errors.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.