> 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-4-upload-data.md).

# Step 4: Upload Data

The *Upload Data* stage of the Restore Wizard is where the restore job performs the record upload into the target Salesforce, showing live progress while running. Here a user can monitor overall progress, object-by-object outcomes, attachment handling, and basic container performance.

![](https://3213705989-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAxXqskcxjs2ntjTUVWmF%2Fuploads%2Fgit-blob-1fb8b8bc4acb30bd9eeba8f2bdcf4474d4182110%2F9a6cfdb5-image1-e1770839972334.png?alt=media)

## Understanding the Dashboard Panels

### **Total Progress**

This is the “big picture” progress for the restore job.

What is seen:

* A step indicator like **“Step X of Y: …”** (example shown: “Step 40 of 40: Restoring Attachment”)
* A status message like **Restore Completed**

How to use it:

* If progress is moving, the job is actively processing.
* If it’s stuck on the same step for a long time, check **Live Performance** and the **Completed Objects** chart for heavy errors or bottlenecks.

### **Attachment Progress**

Tracks attachment/file-type items separately from the main object record restore.

What you’ll see:

* Counts like **Uploaded** and **Skipped**
* Show Details link (bottom-right of the panel)

How to use it:

* If expecting files/attachments to restore and see lots of **Skipped**, click **Show Details** and later review **View Results** to understand what was skipped and why.
* It’s normal for attachments to be processed in their own phase (they’re often heavier and have different constraints than normal records).

### **Upload Rate (Records per Minute)**

A simple throughput graph showing how fast records are being uploaded over time.

How to use it:

* Helpful for sanity-checking performance: if the rate drops to zero while the job isn’t complete, something may be blocked (errors, throttling, connectivity, etc.).
* Small fluctuations are normal; huge flatlines usually mean the job isn’t currently uploading.

### **Live Performance**

Quick view of container resource usage during the restore.

What is seen:

* **RAM Free** (MB)
* **CPU Load** (%)
* **Memory Usage** (%)

How to use it:

* If **Memory Usage** is very high and stays high, restores can slow down or become unstable.
* High CPU during restore is expected; sustained maxed-out CPU + no upload progress is a red flag.

*(This panel doesn’t fix anything by itself – it’s the “is my container dying?” gauge.)*

### **Completed Objects**

This is the most useful panel for understanding what happened per object.

Legend:

* **Restored** (blue)
* **Skipped** (yellow)
* **Errors** (red)

What it means:

* **Restored**: records successfully written to Salesforce for that object.
* **Skipped**: records intentionally not written (common causes: restore type settings, record already exists / doesn’t exist depending on insert vs update behavior, missing prerequisites, or other rules).
* **Errors**: Salesforce rejected the operation or the restore job couldn’t complete it (permissions, validation rules, required fields, referential integrity, etc.).

**Red bars = you need to investigate**. Move to View Results after the job finishes to see the error details and which records failed.

## Common “What am I looking at?” Situations

### **“Why are so many records skipped?”**

Skipped usually means the job decided not to write that record based on rules/settings. The two biggest drivers are:

* **Restore Type**
  * *Insert Only* will skip anything it considers “already exists”
  * *Update Only* will skip anything it considers “does not exist”
* Relationship/order constraints (child record can’t restore cleanly without its parent/state in the target org)

Use **View Results** for the exact per-record reason.

### **“Why are attachments skipped?”**

Attachments/files often have extra constraints (size, permissions, object support, target org state). Use **Show Details** in **Attachment Progress**, then **View Results** for specifics.

### **“I have a big red error bar on an object”**

Finish the run (or stop if it’s exploding), then go to **View Results** and resolve based on the reported Salesforce errors (permissions, validations, missing required fields, etc.). After fixing the root cause, re-run a restore or adjust configuration and **Re-Scan Candidates.**