History and undo

Every successful rule move is recorded in the local mouzi.db database with its original path, destination, rule and time.

History views

The full History view loads the 50 most recent records. The tray popup shows the latest five. Weekly statistics count successful, non-undone moves from the previous seven days.

History is local to the current user profile and is not synchronized between computers.

Undo one move

Choose Undo on an entry while the moved file still exists at its recorded destination. Mouzi attempts to restore the original path and marks the history item as undone.

Undo cannot reliably restore a file when:

• the destination file was renamed, moved or deleted
• the original folder is unavailable or no longer writable
• restoring it crosses file-system volumes in a current release
• another file now occupies the original path

If Undo fails, move the file manually and verify both locations.

Undo all

Undo all attempts to restore the recent non-undone entries. It is not a database rollback and cannot recreate missing files. For a large unexpected cleanup, pause the watched folder first, then undo and inspect the result before changing rules.

Clear history

Clearing history deletes log and statistics records from the database. It does not delete, move or restore files, and it cannot be reversed from within Mouzi.

Back up history

Close Mouzi and copy mouzi.db. The same database also contains settings, rules and watched folders, so treat it as private user data. Platform paths are listed under Settings and local data.

History search and date/type filters are planned but are not available in the current public release.