> 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/core/managing-requests/recreate-a-rejected-or-failed-request.md).

# Recreate a rejected or failed request

Promptly recreate requests which have failed or have been rejected. You can only recreate requests to create or edit an account, a group, a whitelist, a user invitation, or a transaction.

## Before you start

Your Personal Security Device must be connected to your computer, switched on, and the Ledger Vault app opened.

### Instructions

**Administrators: Recreate any request**

1. Click **Requests** on the left panel.
2. Go to the **History** tab.
3. Open the rejected or failed request.
4. Click the **History** tab of the dialog and click **Recreate**.

**Operators: Recreate transactions**

1. Click **Transactions** in the left panel.
2. Click the transaction you want to recreate.
3. Go to the **History** tab of the dialog.
4. Click **Recreate**.

## Results

A pre-filled creation or edit dialog opens. If you're recreating an account, the transaction rules will need to be provided again.


---

# 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/core/managing-requests/recreate-a-rejected-or-failed-request.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.
