Troubleshooting

Start with what FileLever was asked to do

Unexpected results are often explained by the selected mode, scan scope, or preview. Before running the same job again, check:

• the source and target folders, when you are syncing
• the selected sync mode
• the minimum file size, depth, and exclusions, when scanning
• the preview or result groups shown before action
• the visible activity details from the completed run

Common situations

A file is missing from a sync preview

Check whether an exclude pattern, scan scope, or folder selection left it out. Also confirm that the file did not change after the preview was created.

Target-only files were not copied or removed

Target Only means the file exists in the target but not the source. Copy/update leaves it alone. Mirror can remove it after review and confirmation.

A file did not appear in duplicate results

Duplicate File Finder only reports files confirmed to have identical contents. Similar names, thumbnails, or near-identical versions are not an exact match.

A large file is not a cleanup candidate

Size is a starting point, not a verdict. Review the path and purpose; an active project export, backup, or virtual machine may need to remain.

If you still need help

Use the contact form and include the platform, the workflow you selected, the folders or scan scope involved, and the visible details from the run. Avoid including private file contents or credentials.