How to set SharePoint site URLs in Required settings
SharePoint is the most common place where users can lose time by filling the right information in the wrong format. The goal is to give the exporter one stable site URL per referenced list or library so package generation can build clean actions later on.
Enter the site root, not the list page
The exporter needs the owning SharePoint site root, not a list settings URL, an All Items view URL, or a direct item link. If you paste a deeply nested list URL, the action can still fail later because the package builder is trying to compose the site and list references separately.
The easiest test is simple: if the URL ends in a list page or .aspx view, it is probably too specific.
Use https://contoso.sharepoint.com/sites/sales, not .../Lists/Repair%20Labels/AllItems.aspx
Rows should stay in workflow order
If the rows jump around while you type, it becomes harder to compare the page to the workflow. The page should stay in the same order the references were discovered in the source workflow so users can work top to bottom without losing context.
Stable order matters even more when a workflow references similar list names or several task lists in sequence.
Canonical names still matter on export
Sometimes the visible row label and the export-time reference are slightly different because the source workflow exposes a decorated label and the exporter uses a canonical list or library name under the hood. That is why modern matching logic should normalize whitespace and type suffixes while still preserving the visible field you are editing.
If export still says a list is missing after you filled a site URL, the problem is usually stale analysis data or a reference-matching mismatch, not the idea of the site URL itself.