How do I display the "Errors" flagged in progress bar?

[mr-b]

Hi

I'm a new user of FFS and it looks very good. But with a Sync task, the progress bar reports that Errors are present. I've looked in the log folder and there is nothing there!
I'm used to using robocopy and the log file is written to on each file operation.

How do I display the errors?

[xCSxXenon]

There is a log file. After the sync finishes, the status icon next to the sync name in the top-left overview panel can be clicked on to open it.

[mr-b]

Yes as I said I checked the log folder, but that wasn't my question, which was how do I find out about errors *during* the sync job?
If I stop the job it will then have to do the file compare all over again and that takes a long time. The errors must be being saved somewhere.

[xCSxXenon]

Oh, you said

I've looked in the log folder and there is nothing there

so it sounded like you weren't able to find the log file at all. Please clarify; Are you able to find the log file, open it, and it just doesn't show the errors, or you can't find the log at all?

[mr-b]

Ok to clarify, log files are there and readable for completed jobs, but there's nothing present for the currently active job.

[xCSxXenon]

There won't be a log file until the sync finishes

[mr-b]

Why? That could be hours?
Other backup apps append log files as they proceed for atomic file operations. It seems bizarre, notwithstanding fundamentally error-prone, to do otherwise. Stuff happens!

[cpasoft]

Hello everyone...

I have the same question and suggestion for future versions. I also find it useful to be able to check which files are causing problems during sync and not have to wait for sync to finish.

Thank you... :-)

[Zenju]

Then don't select "ignore errors".

[cpasoft]

Then don't select "ignore errors".

Yes, it is an option, but it stops the sync for me and I want it to continue as you are often away from the screen. This way, if there are bad files, the sync has continued and when I come back I can see which files are affected so I can get them from other sources while the rest of the sync continues.

[xCSxXenon]

And that's what the log is for

[mr-b]

I can't quite believe that last exchange!

[cpasoft]

And that's what the log is for

But the log cannot be seen until after the synchronisation is finished, can it?
I would like to see it ‘during’ the synchronisation. We are talking about synchronising external or even remote drives, which can take hours to complete tasks.

By the way, and speaking of log, I have seen that it is not created if the task has not been previously saved. I think a log should be created anyway.

[xCSxXenon]

This is now a feature request:
"View errors in-progress"

[cpasoft]

This is now a feature request:
"View errors in-progress"

Great news!!

Thank you so much. I think this will be useful for many of us...

Regards...

[therube]

(I'd have to agree. Simply Tee the information to a file as progress continues.)

[mr-b]

Great to hear this is coming as it had basically prevented me from using FFS.

[xCSxXenon]

Great to hear this is coming as it had basically prevented me from using FFS.

To clarify, I was simply stating that this thread is more of a feature request than a help thread.
I have no bearing over what features are or aren't considered for inclusion

[mr-b]

Tx for the clarification. I had interpreted it as that "this" i.e. this thread had now been filed somewhere by some kind person as part of a feature request called "View errors in-progress". But I guess not! ;-)

I'd started the thread in the Help section as I'd assumed that a logfile was being written atomically somewhere ('cos what happens if there's a crash or exception?) and that I just didn't know where it was. But I guess not! ;-)

How are new suggested features filed and can they receive comments, upvotes etc.?

[xCSxXenon]

This is usually how features are requested honestly. A dedicated thread in the general category is appropriate if you are coming out of the gate with a request in the OP. Many features have spawned from these types of threads or ones that were initially thought to be bugs. No upvotes or anything, but the dev is quite active throughout, even if they are not posting all the time.

[mr-b]

Again tx for the info, and good to hear the dev is active! :-)