Seems that when upgraded to the 7.0 platform we've had issues (verified on 7.0.2 & 7.0.3 coming from 6.2.2) that On Error settings that are "Only Selected Errors" get reverted back to "All Errors".

I have quite a few delete tasks that do not error on "No File(s) Deleted" but flipped back to All Errors on Upgrade.

Did I miss a note on that?

Have not heard of this problem but we will test this. Thanks for the report.

---

We tested this now but could not reproduce it. We tried creating this specific setting in 6.2.2. and then upgradedto 7.0.3.

However, I do think the problem is that "No files(s) deleted" was never a property of 6.2.2. If you had All errors you will get that "No file(s) delete" by default.

---

We have the same thing when we upgraded. I remember setting the option in 6 to NOT error on when there were no files to act on. After the update to v7, it was reset and I'm having to go back now and reset them all. In my environment, for the most part, we don't want to error if there wasn't a file to act upon, but there are a few instances where a file is expected each time the task runs.

A nice feature would be to define default (global) error settings, while still able to set it at a task level. Perhaps even the ability to change the default error settings and then applying to all/selected tasks where each option is applicable.

I suppose you can get creative and do this with other kinds settings that are common between task types, such as adding/removing conditions and flow/notifications as your environment changes. Or even a task specific setting, such as "delete" after copy in the copy file task across all/selected copy tasks across the jobs. Mass updates would be very cool for job management.