Hi,

It's in there for quite some time now, but I think this should be changed:

When you have a copy files task with multiple copy lines in there, if one of them fails to copy, all the others which come after the failing one, are skipped.
I would prefer to do all the copy lines even when one is failing. Just give the task an error status when one (or more) is failing , but try all the copy lines, not stop.
I'm missing files very often because of this behaviour.

Regards,
Erik

---

Please correct me if I am wrong but I think you can go to On error tab and uncheck IOException and it will continue on errors.

---

What do you say about Post #2? Should we close this?

---

Hi,

I tested today with 8.0.1 (beta) and I think it's not all good. The result of this test is different than I expected..

I have a job with one file copy task.
In this task, with the default settings, I have two file copy lines.
the 1st copies a file which is not there.
the 2nd copies a real file.
The result of this task is success. I think it should fail

If you swap the 1st and the 2nd, result is still success. which fould be failed in my point of view.

If you leave only the file copy line which copies a file which is not there, the task failed. That's good.

If you have multiple copy lines and one will fail, the task result is success, which should be failed...


The above results are different than I expected to be. In version 7 I believe the task fails if a copy lilne fails and stop doing the copy lines in the task after the failed one. In 8.0.1 all the lines are handled (better) but the task result will not be failed if one copy line fails. It only fails when there is only one copy line which fails.

What should be the proper way to do the file copy error handling?

Regards
Erik

---

There is a difference between handling IO errors and the "no files found" error. If the total number of files found is 0 and it is set to raise an error on 'no files' it should raise an error. IO errors are related to permissions = system errors.

---