Details about copy error

Help & Support
1

I am using dopus v13.16. I just copied a folder to a new location and encountered some errors. I did not have "unattended mode" checked and did a "skip all" to continue. Afterwards, I wanted to see the cause of the errors, but I could not find it. I looked in the file log, but all it said was I copied the folder. How can I see the source of the error.

For what it is worth, for this case, I repeated the copy, then enabled unattended mode and discovered that the error was because there were symbolic links to missing files. But I would like to find this out without having to repeat the copy or enable unattended mode - unless that is the only choice. But I see this post, Copy error logs? - #2 by Leo, where Leo said "More generally, there is also the File Log which can be configured to log various levels of detail, not just for unattended operations." But even with maximum logging, I did not see the source of the error.

Thanks!
Phil

2

The errors for individual items are only logged in unattended mode.

Outside of unattended mode, they're only shown in the error dialog, which won't be shown at all if Skip All is chosen.

(The File Log only logs things that were done, not things that were only attempted but didn't happen in the end. That's more for working out where files got moved to if you trigger something accidentally, or reminding yourself what you did previously, and not for keeping a log of errors.)

3

Okay. To confirm: if I need to troubleshoot errors, I have to enable unattended mode?