How do I find out what happened to my restore?
What does the step it stopped at tell me?
A restore that stops can name one of five steps in Stopped at. The step names are the app's own words.
| Stopped at | What it means | What the app says |
|---|---|---|
| Reading the current value | Actorly could not read the field from Shopify, or the record no longer exists. | "Actorly did not change anything. The restore stopped during its checks, before it wrote to your store." with the reason "The record no longer exists in your store." or "Actorly could not reach Shopify." |
| Comparing with the current value | The field no longer held the value Actorly expected, so it refused to write. | "Actorly did not change anything." and the reason "The value changed again since this change was recorded." |
| Writing the value | Shopify refused the write, or the answer was unclear. | "Shopify refused the change." or "The restore did not complete. Your store may be unchanged, or partly changed." |
| Reading it back | Actorly could not read the value after writing. | "may be unchanged, or partly changed" |
| Checking it matched | The value Shopify now holds is not the value put back. | "Shopify took the change, but the value read back did not match." |
A restore that Actorly refuses before any step, such as one for a deleted item, a field not on the restore list, or one over your plan's allowance, shows its message at once and does not appear on Recovery jobs. If a check before the write fails, nothing is changed. After the write, Actorly cannot always tell, so it asks you to look rather than assume.
What does each reason mean?
When a restore stops, the app may show one short reason from a closed list, decided from the step, not from Shopify's own text.
| Reason | What to check |
|---|---|
| Shopify refused the change. | Open the field in Shopify and read what it holds. Then try again. |
| The value changed again since this change was recorded. | Open the field and read what it holds now. Look at the newer change in Changes. |
| The record no longer exists in your store. | Check the item in Shopify. Actorly cannot bring a deleted item back. |
| Actorly could not reach Shopify. | Try again in a moment. |
| Shopify took the change, but the value read back did not match. | Open the field in Shopify and read what it holds now. Your store may already be changed. |
| Actorly could not finish this restore. | The app does not give a reason. Check the field in Shopify and give support the Job ID. |
What does Declined mean?
Declined - it had changed is Actorly working as designed. The field no longer held the value Actorly expected, so Actorly stopped at its comparison and wrote nothing. The message begins "Actorly did not change anything." and tells you to look at what changed first. For a single field the expected value is the one Actorly reads when you confirm, so this happens when the field changes at that moment. In a restore to a date and time, the expected value is the one in the summary you approved, and a declined field is left alone and listed while the others carry on: "Declined means the value in your store had changed since the summary, so Actorly left it alone rather than overwrite a newer edit."
What does Outcome unknown mean?
The restore stopped midway, and Actorly lost track of it: "Actorly lost track of this restore. Your store may or may not have changed, so check this resource's history before trying again." Actorly later re-reads Shopify and settles the row only when the evidence is conclusive: the live value matches the target (Put back), matches the value before (Did not complete), or matches neither (Declined). If it cannot tell, the row stays Outcome unknown. For a job of several fields the window says: "Actorly lost track of this job. Items that were midway may or may not have changed your store, so check those resources before running it again."
What should I check in Shopify?
- Open the resource and read the field. Compare it with the three values the restore showed: what it held before, what it held now, and what it would be put back to.
- Check the change history in Actorly. Open the change and read Restore history and History of this record. If the write did reach Shopify, the new value shows in Changes as an ordinary change, not one marked as a restore.
- Do not retry blindly. For Outcome unknown and Did not complete, check first. For "Too many restores in the last minute", wait a moment.
What do I send support?
The Job ID for support shown on the restore, the step it Stopped at, the resource's name and when it happened. You can start a chat from the footer: see Chat with Actorly support from inside the app.
A worked example
Sample: you restore a product's tags and the window ends with "The restore did not complete. Your store may be unchanged, or partly changed. Check the resource in Shopify before trying again." and "Stopped at: Writing the value". You open the product in Shopify: the tags are unchanged. Actorly could not confirm that when it stopped, which is why it asked you to look. You try again and it ends Restored. In a second case the row reads Outcome unknown because Actorly's processing stopped midway; you open the product, see the new tags are in place, and later the row settles to Put back once Actorly re-reads Shopify. In a third case the restore begins "Actorly did not change anything.", the row reads Declined - it had changed, and nothing was written.
Frequently asked questions
Is my store changed if a restore did not complete?
If a check before the write failed, nothing was changed. If the write was sent and Actorly could not confirm the value, your store may be unchanged or partly changed: look at the field in Shopify before trying again.
What does Declined mean?
The field no longer held the value Actorly expected when it checked, so Actorly wrote nothing. It protects the newer edit.
Why does it say I have used my restore?
Actorly Watch includes one restore in any rolling 30 days. The message says "You have used the restore included in your plan in the last 30 days. Actorly Restore includes unlimited restores." A restore that succeeded counts, and so does one still running, for up to 5 minutes. A refused, declined or failed restore does not.
What if some fields in a multi-field job were declined?
Declined means the value in your store had changed since the summary, so Actorly left it alone. Items already put back stay put back.
Should I try again straight away?
For "Too many restores in the last minute", wait a moment. For Outcome unknown or Did not complete, check the resource in Shopify first.
Can Actorly retry for me?
The app does not say that it retries a restore. A restore that Actorly refuses before it starts is not recorded on Recovery jobs; one that started has its outcome there, and the app asks you to check.
Where is the list of every restore?
On Recovery jobs. See Check how a restore ended on Recovery jobs.