Retry, Check again, Read again: which button does what
What the buttons for doing something again do: Retry, Check this file again, Check again with version, Read again and Retry safely, and when each is available.
- 4 min read
- Updated October 13, 2026
Content Uploader never repeats something on its own that could surprise you, but it gives you a button for each kind of "do it again". They differ in what they redo.
| Button | Where | What it redoes | Available |
|---|---|---|---|
| Retry | The red box This file could not be processed | Continues the stage that failed (reading, or preparing and comparing) | While the original file (for a reading failure) or the stored rows are still kept |
| Read again | Footer of a file's page, next to First row (and Separator for a CSV file) | Reads the original file again with the first row and separator you chose | Before the file is published, while the original is kept (30 days) |
| Check this file again | Boxes on the review that mention new categories or tags, and after Publishing is refused | Compares the stored rows with the site now and with the newest mapping | While the file has not been published |
| Check again with version N | Footer, when a newer version of the configuration exists | Checks the file again with that version | Same |
| Update mapping for this file | This file doesn't match the configuration | Opens the editor for this file; saving checks it again | While the file has not been published |
| Show the latest / Show the new results | A notice that the file was checked again | Shows the newest check of the file (nothing is redone) | When a newer check exists |
| Retry safely | Sites → Publishing results, per item | Sends one failed item again with the same operation, which cannot create it twice | For items that failed, are still queued, or were interrupted |
Retry#
A file could not be processed when it could not be read, or when preparing or comparing was interrupted (for example, the check was cut short). The page says why. Retry continues from the stage that failed. If the problem is the file itself (an unsupported format, a damaged file, unreadable text), retrying does not help: use Or upload a corrected file. The file cannot be read lists the messages. A run that makes no progress for ten minutes is also picked up again automatically.
Retry is disabled when it would need something that has been deleted: The source was removed after 30 days. Upload it again to retry. or The rows were deleted a year after upload. Upload the file again.
Read again#
The page's footer says how the file was read, and lets you read it again another way:
- First row: Column names, or Data (no header row) for a file whose first row is already an item. Without a header row the columns are named Column A, Column B and so on (files without a header row).
- Separator, for CSV files only: Comma, Semicolon or Tab. If the columns look wrong (everything in one column, or a value split in two), choose the right one. The configuration's last separator is preferred when the file is ambiguous.
When you change either, the button Read again appears, and the file is read again from the start. Its columns are then checked against the configuration again, so a file read the other way usually needs Update mapping for this file.
Check this file again#
A check is a snapshot: the file's rows, compared with what was published and with the site at that moment. If anything changed since (you mapped a field, someone added the missing category on the site, another file was published, the site's fields changed), the old snapshot is out of date. Check this file again takes a new one from the same rows, without uploading anything. You can do it as often as you like before the file is published, and each new check replaces the previous one; a page that shows an older check says so and offers Show the latest.
Publishing is refused and this button is offered when the snapshot would be unsafe to publish:
- Another file was published after this one was checked. Check this file again to see its current changes.
- The destination's fields changed after this file was checked. Check the file again to continue.
- This file was checked again after you opened it. Review the new results before publishing.
Retry safely#
On the Sites page, each result shows its attempts. An item that failed (after Content Uploader already retried a transient problem a few times), or that is still queued or sending after an interruption, has Retry safely. It sends the item again with the operation ID of the first try. Your site's connector remembers that operation, so a retry that reaches a site which had in fact already saved the item returns the stored result instead of creating a second item. An interrupted attempt can be resumed after five minutes. See retrying failed items.
When there is nothing to redo#
A file that has been published keeps its result. To publish another version of the same file, upload it again: unchanged rows are shown as unchanged and only the differences are sent.
Was this article helpful?
Related articles
- Importing dataThe Uploads page and what each status meansThe list of every file you uploaded, filtered by configuration, with its status (Reading file to Needs attention), its counts and its date, and what each status means.
- Importing dataEdit a configuration and how versions workChange a mapping safely: each save makes a version, files keep the version they were checked with, a new version can be applied to a waiting file, and conflicts are flagged.
- Reviewing and publishingRetry failed items safelyHow to find the items that failed to publish, fix the cause, and send them again with Retry safely without creating duplicates, and when to upload the file again instead.
- TroubleshootingThe file cannot be read or is refusedWhat to do when a file is refused on upload or the page says This file could not be processed: every message, its cause and the fix, for spreadsheets, CSV files and ZIPs.