> For the complete documentation index, see [llms.txt](https://learn.capstorm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.capstorm.com/capstorm-container/reference/restore-wizard/step-6-summary.md).

# Step 6: Summary

This is the final step of the wizard. It gives you a **high-level report** of the restore job: what ran, where it restored to, how many records were restored/skipped/errored, and an **activity log** you can use for auditing and troubleshooting.

![](https://495509274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDAPx1zE2IARmzGMaHbAx%2Fuploads%2Fgit-blob-fb4c0386985fabba61b0ee68943a23692fdb6c45%2F2171cbd8-image2-1024x489.png?alt=media)

## Details Section

The **Details** panel summarizes the restore job configuration you ran:

* **Name** – the restore job name you entered in Configuration.
* **Parent Object** – the top-level object you restored (example shown: **Account**).
* **Source Connection** – the backup database/source used for the restore (example shown: **PostgreSQL**).
* **Type** – restore type used (example shown: **Insert And Update**).
* **Target Connection** – the Salesforce org connection restored into (example shown: **Sandbox**).

Use this section as your “receipt” to confirm:

* You restored the right object(s),
* From the right backup source,
* Into the right Salesforce org,
* Using the intended restore mode.

## Records Restored Section

This panel gives an at-a-glance breakdown of restore outcomes using a pie chart and counts.

### **Object filter**

There’s a dropdown above the chart (example shown: **All Objects**) that lets you switch between:

* A combined view across everything restored (**All Objects**), or
* A specific object view (useful if one object had lots of skips/errors).

### **Status categories**

The results are grouped into three buckets:

* **Restored** – records successfully written to Salesforce (inserted and/or updated).
* **Skipped** – records not written due to restore rules or conditions.
* **Errors** – records that failed due to Salesforce/API/validation/permission issues.

### **“Click to view” links**

Next to **Skipped** and **Errors** you’ll see **Click to view** links. Use these to jump directly into the underlying details (so you can see *which* records were skipped/errored and why).

#### **How to interpret the chart**

* A lot of **Skipped** can be normal depending on restore type (Insert Only / Update Only) and the state of the target org.
* Any meaningful **Errors** should be reviewed-errors mean Salesforce rejected changes or the restore couldn’t complete operations as planned.

## Activity Log Section

The **Activity Log** is a timeline-style log of what happened during the restore (status updates, steps, notable events).

### **Time range dropdown**

You can filter the log by time window:

* **All Time**
* **Last Year**
* **Last Month**
* **Last Week**

Use this when:

* You run multiple restores and want to isolate the relevant one,
* You’re comparing outcomes across runs,
* You’re troubleshooting something that happened recently.

### **Log grouping**

Entries are grouped (example shown: **Today**) and show how many log entries exist for that period.

## Finish

### **Recommended “wrap-up” workflow**

Before clicking **Finish**:

1. Check the **Details** panel to confirm you restored into the correct target org.
2. Review the **Records Restored** breakdown.
3. Click into **Errors** (and **Skipped**, if unexpected) to confirm you understand the outcomes.
4. Use the **Activity Log** time filter if you need to capture troubleshooting notes for support/audit.
