# The Activity log

**History → Recent activity → View all activity.**

Every run Snapty has made on your store, newest first — checks and restores in one table. The dashboard and the History screen show the newest few; this screen shows all of them, paged.

There is no search box, no filter and no sort. A run has no name to search for, and a log has one meaningful order: the one things happened in.

## The columns

| Column | What it holds |
| --- | --- |
| **When** | When the run finished, with how long ago beside it |
| **Theme** | Which theme the run was about. Blank means Snapty never established which theme was live |
| **Result** | The outcome — see the two tables below |
| **Files processed** | How many files the run accounted for. This is the *"and it was complete"* half of a result |
| **Took** | How long the run took. Blank while it is still running |

## Two kinds of row, one table

**A check** carries its trigger — *first seen · on schedule · publish · you asked · before a restore* — the same words as the timeline.

**A restore** carries its kind — *restore, one file* or *restore, whole version* — plus:

- the **file path** it put back, for a one-file restore. One path is the whole answer; a count is not;
- the **theme it wrote into**, as Shopify named it at the time. For a restore into a copy, that is the copy — not the theme it was made from. For a whole-version restore, **Files processed** is how many recorded files went into the copy.

## Results of a check

| Result | What it means | Was anything written? |
| --- | --- | --- |
| **Running** | Still going | — |
| **Recorded** | Something differed, and a new recording was written | A recording |
| **No change** | Every file matched what is already recorded. The normal result on a healthy store | Nothing |
| **Partly unreadable** | A recording was written, but some files could not be read. They are marked unreadable rather than assumed unchanged | A recording, with gaps named |
| **Failed** | The check stopped before it finished reading your theme | Nothing. Nothing on your store was changed |
| **Interrupted** | Snapty restarted while the check was running, so it reached no result. The next check runs on schedule | Nothing. Nothing on your store was changed |

<Hint type="warning" title="Partly unreadable is not a success">

Snapty says so rather than reporting a clean recording that quietly covers fewer files than your theme has.

</Hint>

<Hint type="info" title="Interrupted is not a failure">

The run did not fail; it never finished. A deploy on our side is the usual cause.

</Hint>

## Results of a restore

| Result | What it means |
| --- | --- |
| **Restored** | The theme reports the recorded content. The file, or the version, is back |
| **Already in place** | The file already held exactly the recorded content, so nothing was written. Not a failure — writing a file back byte for byte would leave no trace, so Snapty checks first and says which happened |
| **Not confirmed** | The write happened, or was attempted, and the result could not be confirmed. The reason line says which case |

## The reason line

A row that did not succeed carries one line under it, written for you — never the raw error.

| Reason | What it means | What to do |
| --- | --- | --- |
| The check stopped before it finished reading your theme | A capture failed partway | Nothing on your store changed. The next check runs on schedule; if it repeats, contact support |
| Snapty could not confirm which theme is live, so the check never started | Shopify did not answer which theme is published | The next check asks again |
| Shopify refused the write | Usually a permission this store has not granted | Re-open Snapty from your admin and accept the permissions, then restore again |
| The file was written and the theme does not report the recorded content | The write went through; reading it back gave something else | Check the file in your theme editor. Restore again if it is not what you expect |
| Shopify was still working when Snapty stopped waiting | The write may well have succeeded; it could not be confirmed in time | Look at the file in your theme editor. Restore again if it did not land |
| The recorded copy is no longer in storage | Nothing to put back | Pick a more recent recording of the same file |
| This snapshot holds no recorded copy of that file | The file was not in the theme when this recording was taken | Pick a later recording |
| That version is no longer recorded | The recording rolled off | Nothing to restore |
| The recorded file belongs to a different theme | The restore was refused before anything was read | Open a recording taken from the theme you are fixing |
| The copy was made and some recorded files are not in it | A whole-version restore where some files did not land. The copy exists and is usable | Check the files that matter before publishing the copy |

## View snapshot

A link on rows that left a recording in force — the one a check wrote, or the one a restore confirmed. Absent when the run left none.

## When a figure shows "—"

It means the figure was never written down, not that it was zero. Runs from before the log kept that detail show a dash. An interrupted run shows no duration, because the time it stopped was never recorded — only the time we noticed.

## Empty state

> *"No check has run yet. The first one starts on its own; you can also take a snapshot now."*

## What the log answers, and nothing else does

1. **Is Snapty actually running?** A timeline that has not moved does not tell you. A log full of **No change** rows does.
2. **What happened to that restore?** The row names the theme it wrote into and the outcome, including the case where it deliberately wrote nothing.