> 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/snowflake-salesforce-connector/reference/restore/step-5-view-results.md).

# Step 5: View Results

The *View Results* stage is where a user can **review exactly what happened** during the restore, broken down by Salesforce object and record. Use it to confirm success, investigate errors, and understand why any records were skipped.

![](/files/n4FDBltSqeL7X2h3tjoH)

## Using the Filters

### **1) Object**

Select the object to analyze (Account, Contact, etc.). This page shows results **one object at a time**.

### **2) Fields**

Use this to control which columns appear in the grid.

* Keep it small when you’re troubleshooting (ID + name + status + a couple key fields).
* Add more fields when needing to verify that specific values restored correctly.

### **3) Record Type**

This filters the grid based on restore outcome. Options are:

* **All** – shows everything.
* **Pending** – records that are still being processed (mostly useful if you open View Results before the restore is fully finished).
* **Skipped** – records that were not restored (use **Show Skipped Reasons** to see why).
* **Inserted** – records that were created in the target org.
* **Updated** – records that already existed in the target org and were modified.

## Understanding the Results Grid

Common columns seen:

* **Original Id** – the record ID from the backup/source dataset.
* **Restored Id** – the record ID in the target org after the restore.
  * For **Inserted** records, this may be a newly created ID.
  * For **Updated** records, it may match the existing target record’s ID.
* **Status** – the outcome for that record (Inserted / Updated / Skipped / Pending).
* Additional columns (like **Account Name**, timestamps, audit fields, etc.) depending on the **Fields** selection.

## Troubleshooting Workflow

1. Set **Record Type = Errors**
   * If there is not an “Errors” option in the dropdown, instead click **Show Errors** to view the error details directly.
2. Fix the root cause in Salesforce (common themes: validation rules, missing required fields, permissions, duplicate rules).
3. Return here to confirm the error count dropped and records moved to **Inserted/Updated**.

For skipped records:

1. Set **Record Type = Skipped**
2. Click **Show Skipped Reasons**
3. Look for patterns (restore type mismatch is the classic one: *Insert Only* skips “already exists”; *Update Only* skips “does not exist”).


---

# 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://learn.capstorm.com/snowflake-salesforce-connector/reference/restore/step-5-view-results.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.