Repository navigation
Undo and recovery
Most of the time, you just need the result: the files arrived, the archive was created, or a name changed. Traverse records eligible changes so you can undo them without rebuilding the steps yourself.
Use Undo File Operation for the eligible recorded change. You can also inspect the operation's result first. Undo can survive an app restart, but it checks the current files again: a changed item or occupied original name can prevent a safe reversal.
Skip leaves a conflict alone. Keep Both chooses a numbered name. Replace and folder Merge, where offered, require an explicit choice. A move across volumes keeps the source until the destination has been validated and committed.
Open Results or the operation history and look at the affected item. A stopped, partial or uncertain outcome isn't the same as a completed copy. Stop requests cancellation; cleanup can still need time before the job settles.
Avoid retrying an uncertain remote write or deleting its retained work just to clear the list. Review what was submitted, what remains locally and whether the connection is available. For remote editor conflicts, Before Save and Edited Text let you compare the captured versions without reconnecting.
Move to Trash uses macOS Trash. Traverse Trash groups the items Traverse recorded, so you can restore an eligible deletion session together. It doesn't replace Finder's Trash or display everything other apps deleted.
Restoration checks for changed files and occupied names. Permanent deletion, where offered, is a separate confirmed action. Removing saved editor versions has its own consequences for those versions' Undo; it doesn't delete the original document.
The file-operation guide describes the safeguards. If a result is confusing, tell us the action and exact status in a bug report, with private names removed.
Found a missing step? Improve a guide or ask the community. Check your download's release notes for version-specific behavior.