> 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/copystorm-restore/reference/restore-plan-tab/restore-order-detail.md).

# Restore Order Detail

The Restore Order Detail tab lists the order in which tables will be written to Salesforce according to the list specified in the Restore Order tab.

The following examples reference the screenshot below.

If a table name appeared in the Required Prerequisites column for Account it means that CopyStorm/Restore’s table scanning algorithm decided to write Account records to Salesforce even though the Account table contains a non-nillable reference column referencing a table later in the list of tables to be restored. In practice, this should never happen in a plan built by CopyStorm/Restore. However, if it does, this plan will show the issue and allow overriding Salesforce dependencies to fix the problem.

If a table name appeared in the Nillable Prerequisites column for Account it means that CopyStorm/Restore’s table scanning algorithm decided to write Account records to Salesforce when the Account table had a nillable column referencing a table later in the list of tables to be restored. This condition happens fairly frequently in Salesforce, and CopyStorm/Restore attempts to reduce the impact on restoration performance by optimizing table ordering. This condition is not an error but means that CopyStorm/Restore will patch up nillable reference fields in a second pass, after the records have been restored.

![](/files/Ulacrb1lhE3agy87a2fU)


---

# 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/copystorm-restore/reference/restore-plan-tab/restore-order-detail.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.