> For the complete documentation index, see [llms.txt](https://docs.flosum.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flosum.com/backup-and-archive/restore/execute-restore/running-a-restore-job-execution.md).
# Running a Restore Job (Execution)
{% hint style="success" %}
#### Required User Credentials
\[**Flosum User**] - **Backup & Archive** license with **Restore** permissions
{% endhint %}
## Overview
This article covers the second stage of restoring data in the Flosum Backup & Archive app. In this step, you run a Restore Request to load your backed-up data into your Salesforce organization. The restore process works the same way for both Backup and Archive Restore Requests. See the following articles for instructions on creating restore requests.
* [Creating a Backup Restore Job (Preparation)](/backup-and-archive/restore/prepare-restore/creating-a-backup-restore-job-preparation.md)
* [Creating an Archive Restore Job (Preparation)](/backup-and-archive/restore/prepare-restore/creating-an-archive-restore-job-preparation.md)
{% hint style="info" %}
As of **Summer 2025**, Flosum introduces a more transparent and auditable restore experience, including enhanced visibility into restore results directly from the **Restore Job view**.
{% endhint %}
During this phase, you'll review the data retrieved from your Restore Request to confirm that the correct data will be restored. Once you verify the Restore Request contains valid data, you can proceed with restoring it to your selected Salesforce organization.
After the restore is complete, you can log in to your Salesforce org and verify that the records were restored correctly.
## Run a Restore Job
{% stepper %}
{% step %}
### Select a Restore Request
1. Click **Restore** from the sidebar menu.
2. Click the **Organization Switcher** from the breadcrumb path.
3. Select the organization you wish to restore.
4. Click the **History** tab.
5. Click a **Restore Request** job that is marked as **Ready for restore**.
{% hint style="info" %}
Only **Restore Requests** that have one or more **Records** will be marked as **Ready for restore**.
{% endhint %}
{% endstep %}
{% step %}
### **Review the Restore Request**
Before restoring data, it is recommended to review the request and the data to be restored.
1. Test.....
2. Review the information on the **Overview** tab to verify that the data source and the number of records to restore are correct.
3. Click the **Data** tab to view the data to be restored.
4. Click an object to view the records for that object.
5. Click a record to view the fields for the record.
6. Review the field data to ensure the correct records are selected to restore.
7. Click the **Logs** tab to view the Objects and Log for this restore request.
{% endstep %}
{% step %}
### Run Restore
Once you're satisfied with the data to restore, you can proceed to run the **Restore**.
1. Click **Run restore**.
2. Click **Run restore** on the **Run restore** confirmation dialog box.
3. After starting the restore job, you will be taken to the **Restore > History** tab.
4. The table shows the status of the Restore job.
5. Once the **Restore** is complete, you can view the restored data in your Salesforce organization.
{% endstep %}
{% endstepper %}
---
# 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://docs.flosum.com/backup-and-archive/restore/execute-restore/running-a-restore-job-execution.md?ask=&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.
