# A restore was refused

A refusal happens on the confirm step, before anything is written. Nothing on your store has been touched. The screen names the cause; this is the short list of what each one needs.

| What you see | What to do |
| --- | --- |
| **That theme is no longer on this store** | The theme was deleted from Shopify. Nothing can be restored from this recording; it stays readable |
| **This file was recorded from a different theme** | You are looking at a recording of another theme. Open one taken from the theme you are fixing |
| **Snapty cannot write to your theme files yet** | Open Snapty from your Shopify admin and accept the updated permissions, then try again |
| **The recorded copy is no longer in storage** | Its contents aged out. Pick a more recent recording of the same file |
| **This snapshot holds no recorded copy of that file** | The file did not exist yet. Pick a later recording |
| **This version is no longer recorded** | The recording rolled off. Check the timeline for what is still kept |
| **Snapty could not read the whole of that theme just now** · **Snapty cannot say where this file would land** · **The restore could not be started** | A request to Shopify or to the queue did not get through. Try again in a minute |

The full table, with what each case means, is on [Restoring](https://docs.foxecom.com/snapty-app/history-and-restore/restoring#refused-before-anything-is-written).

## If the restore ran and was reported as Not confirmed

That is not a refusal — the write was attempted. The reason line on the activity log says which case: see [The Activity log](https://docs.foxecom.com/snapty-app/history-and-restore/the-activity-log#the-reason-line).