No retry option when owerwriting from an archive

[avada]

When a file is locked in this case, I only get the options: cancel, skip and rename.
I usually want to overwrite files for a reason. Sometimes this file is locked unexpectedly, which I usually can fix by closing the offending app.

Renaming doesn't do at all what I want, retains the old file and renames the new one to something I don't want.
If I either cancel or skip I have to to re-copy all the files in practice.
Trying to make note of where I cancelled or which files I skipped is just a recipe for "disaster".

A retry option would be a neat and simple solution to this

[ghisler(Author)]

The problem is that when the error occurs, it may not be possible to go back (e.g. because it's a solid archive).

[avada]

The problem is that when the error occurs, it may not be possible to go back (e.g. because it's a solid archive).

I don't see why there's a need to go back?
It seems to me that TC stops at the right spot, otherwise the option "rename" wouldn't be possible. A retry option would be much the same, only trying to write the same file again instead of renaming.

Edit:
Just did a quick test and renaming works when copying from a solid archive to a locked file, even if at first I provide provide a filename that belongs to a file that's also locked. Actually it's exactly what a retry option would do, if I provide the same filename.

[ghisler(Author)]

OK, I have added this now, please try it! Target needs to be locked, e.g. open in Word or other locking editor.

[avada]

OK, I have added this now, please try it! Target needs to be locked, e.g. open in Word or other locking editor.

Great! Tried it. Seems to work fine.

(It's slightly odd, that the overwrite prompt appears after the "file is locked" prompt. Only if the locked file in question is the first file to be overwritten)

[ghisler(Author)]

Yes, that's for "overwrite all".