---
id: troubleshooting.rolled-back-some-couldnt-be-undone-conflict
url: https://storagestudio.us/faq/troubleshooting/rolled-back-some-couldnt-be-undone-conflict
category: "Troubleshooting & messages"
subcategory: "Undo, move back and Recycle Vault"
question: "What does \"couldn't be undone because of a conflict\" mean after a roll back?"
alt_questions:
  - "rolled back couldn't be undone because of a conflict"
  - "roll back conflict storage studio"
  - "some items not restored undo"
  - "undo skipped items"
short_answer: "Something new now sits at those items' original places, and rolling back would overwrite it — so they stayed safely on the drive. Move the new item aside and undo again."
tags: ["undo", "conflict"]
related: ["https://storagestudio.us/faq/troubleshooting/something-else-now-exists-at-original-place"]
applies_to: "all"
last_reviewed: 2026-10-01
---

# What does "couldn't be undone because of a conflict" mean after a roll back?

Most items were put back, but for some, something new now exists in the original place — a file or folder with the same name that wasn't there when the move happened. Rolling back would overwrite it, so Storage Studio left those items safely on your drive instead.

Look at the original location: if the new item is something you don't need, move it aside and run the undo again for the remaining items. Nothing was deleted either way.