> For the complete documentation index, see [llms.txt](https://docs.tipo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tipo.io/backup-and-restore-tipo/help/troubleshooting/restores.md). # Restore problems Fix restores that cannot start, finish with errors or do not change anything. Use this page when a restore will not start, ends with errors, or finishes without changing your store. ## Messages before a restore starts These appear as a banner or a message on the review step of the restore. | Message | What it means | What to do | | ------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **A restore is already in progress for this store.** | Only one restore runs at a time. | Wait for it to finish. Open [Restore history](/backup-and-restore-tipo/restore/restore/restore-history.md) to follow it. | | **A backup is in progress for this store. Wait until it finishes before starting a restore.** | A backup is running. | Wait for the backup to finish, then start the restore again. | | **Backups and restores are paused** (also "Restores are paused: this store is over its plan.") | Your store uses more than your plan includes. | Upgrade or free up space. See [Plan and billing problems](/backup-and-restore-tipo/help/troubleshooting/billing.md). Nothing you backed up is deleted. | | **This store has no completed backup yet to compare against.** | You have no completed backup yet. | Run **Back up now** from Home and wait until it shows **Completed**. | | **This backup is past your plan's retention window. Only single items can still be restored from it.** | The backup is older than your plan keeps backups. It can no longer be restored as a whole. | Pick a newer backup, or choose **Choose specific items** to restore single items from it. | | **This upload is no longer available to restore.** | An uploaded file is only kept for about 24 hours. | Upload the file again. See [Restore from an exported file](/backup-and-restore-tipo/restore/restore/restore-from-a-file.md). | | **Confirm that this uploaded file may change customers or theme code before restoring.** | The file includes customers or themes and the confirmation box is not ticked. | Tick **I understand this file can change customers and theme code**. | | **Couldn't load what changed** | The comparison could not be loaded. | Select **Try again**. | ### An upload will not start * "An upload is already being validated for this store." Wait for the current check to finish. * "You've uploaded several files in a short time. Wait a few minutes, then try again." * "Zip files only." Choose the `.zip` file you exported from the app. * "This file couldn't be used." The file is not a valid export. Download the backup again and upload the new file. ## Restore finished, but something is missing ### "Restore finished with errors" Some items failed or had conflicts. Open the details: {% stepper %} {% step %} On the finished panel, select **View failed items** or **View conflicts**. You can also open **Restore history** and select the date. {% endstep %} {% step %} Read the **Details** column for each item. It gives the reason. {% endstep %} {% step %} Fix the cause if you can, then restore those items again. A new restore only changes what is still different, so it is safe to repeat. {% endstep %} {% endstepper %} See [Follow a restore and read the results](/backup-and-restore-tipo/restore/restore/follow-a-restore.md) for what each result means. ### Conflicts A conflict means the app skipped an item because it could not be put back safely. Common reasons: * **A blog post whose blog is gone.** The message says the item "depends on something that isn't in your store anymore". Restore the blog first, or include **Blogs** in the same restore. * **The backup does not record the blog or theme an item belonged to.** The item cannot be recreated. Restore a newer backup if you have one. * **A metafield definition whose type differs** from the one in your store. The app does not change the type. * **A standard definition from Shopify.** Shopify does not allow changes to it. ### "Nothing was restored" The restore ran, but your live store already matches the backup for everything you asked to change. This is not an error. Possible reasons: * The item is already the same as the backup version. * You restored only a part of the product that did not differ. Try restoring other parts too. * The backup has no sales channel data for the product. Run **Back up now**, then restore again. * The item depends on something that is gone, such as a blog. See the conflicts above. ### Some items were "Partly restored" This happens with themes. Some of the theme's files were written and some failed. The failed files are listed. Restore again: only the files that still differ are written. ### A deleted theme cannot be restored into itself If a theme was deleted from your store, restoring it into the same theme is not possible. Open the theme as described in [Restore a theme](/backup-and-restore-tipo/restore/restore/restore-a-theme.md) and choose **A new theme** in the restore window. Follow the message in the window if it differs from the hint on the theme page. ### Some data is not restored at all Orders, inventory quantities and locations, policies, saved searches and shipping zones are backed up so you can view and download them, but they cannot be restored. Customer passwords and payment details are never restored. See the [FAQ](/backup-and-restore-tipo/help/faq.md). ## A restore stopped or failed ### "Restore stopped" Someone stopped the restore. Items already written stay restored. Items not started were left as they were. ### "Restore failed" and "The restore stopped because of an error" A message from the system follows. Items listed as restored stay restored. Try again. If it fails again, [contact support](/backup-and-restore-tipo/help/contact-support.md) and include the date of the restore. ### "The safety backup did not finish, so nothing was written to your store." The restore stopped before changing anything. It is safe to start it again. See [Safety backups and undoing a restore](/backup-and-restore-tipo/restore/restore/safety-backups.md). ### "Your backup storage is nearly full." The safety backup still runs, but it may take your store over its plan. After that, backups and restores pause until you upgrade or free up space. ## Next steps * [Follow a restore and read the results](/backup-and-restore-tipo/restore/restore/follow-a-restore.md) * [Restore history and details](/backup-and-restore-tipo/restore/restore/restore-history.md) * [Safety backups and undoing a restore](/backup-and-restore-tipo/restore/restore/safety-backups.md) * [Contact support](/backup-and-restore-tipo/help/contact-support.md)