TC should wait not error in some cases. (Error 21: Device not ready)

I've been trying to move a huge steam library across to my backup NAS server to rejig my array in my computer. However, I notice that some of the errors I was getting was error 21 device not ready.

I know that TeraCopy will wait for a target to come back online on currently active Transfers as it will show this in yellow when this is the case. However, other files seem to just get skipped over when using the multi threading.

In these scenarios, I believe TeraCopy should wait for the device to be ready and try again, Rather than just logging it as an error and continuing on. This is because that this problem can persist for thousands of errors until the device eventually reports it's ready again, Meaning thousands of transfers that need to be tried again.

This can also be a problem if you get an error for target not found. If you're overwhelming a NAS server, It may drop the service that's facilitating the transfer until it is ready, and then bring it back online. (SAMBA,NFS,ISCSI,etc.)

This causes a problem if you want to leave the transfer unattended overnight for it hopefully to be done next day or come back when it's done. It could even be an option where you can set the retry timer and the amount of retries it should do before moving on. This would give a good level of customization to the transfer, and allow you to set and forget when sending to a unstable or slow target such as a network share or Spinning rust.

It could even be that these are skipped over in its own separate class of error, and even tried again at the end of the transfer should it be skipped dew to the max wait time being reached. When such an event happens and it is waiting, A clock icon could be shown next to the files affected in the transfer. If the timeout is reached and fails again, It could then have a yellow clock icon Indicating the timeout limit was reached and the software moved on. At the end of the transfer, it then does a last attempt to try again, Counting down till it reaches the max retry limit. Shall this fail. It is then classed as failed and logged as an error.

This retry mechanism would also be helpful in circumstances where a drive may just have a transitory error, Something that is likely to happen if you are blasting data at a target.