yeah this is set to "skip". i just wonder "why" there's an error. besides as i realize that this issue often appears if you just abort some transfer and then switch to another source or folder , queue this and that and then fire up again the resume_queue , i had this on local transfer, i have this on fxp transfers!
not often, not all the time, but sometimes and after manually again starting those "aborted/skipped" ones then it's working. but why? there must be some reason, i think regardinbg folder cache or sth...
|
Threaded Mode