I am testing failure notifications to make sure they work. When setting up a task to fail, so that I can see the failure notification, I find that sometimes the task in VC completes successfully, even though it did not.

For example, I have a task to export the settings for VC; and I want to be notified when it fails. So I deliberately gave it an incorrect path name for testing, so that I could see the failure notification, and I found that the task ran successfully, although of course it did not. What would you suggest in this type of situation, to be able to correctly identify the failure?

There could be Tasks where we not capture all kind of errors. If you find any please report to us which Tasks that does not report correctly and we will fix that. We will look at the Export Task now.

---

A note on this: When a print task fails, the job and task still say success even though an error shows up in the log. I've not tried the notification in conjunction with this, but it could be a bit confusing looking at the client when you see all the green check marks but nothing is printing.

I think this was fixed in 4.8.4. but I will verify this.

---

Another task is FTP. Ideally, I would like to be able to FTP a group of files together, and receive a notification if any fail to deliver. (Still trying to resolve this with using conditions.) However, if I use a separate upload for each file; or even a separate FTP task for each file, it does not fail, even if there is no file to FTP.

It seems to be a need for you to define what actually is an error in each Task. Because, for example, some may find that when no files was downloaded is OK and other see it as an error. We will think about ways to defined what is an error or not in each task.

---

It seems to be a need for you to define what actually is an error in each Task.

1) Export task: if the backup file is not created, that would be an error. An example of when that might happen would be if the network path were unavailable when the task runs.

2) FTP task: if the file to be FTP'd is unavailable when the task runs at its scheduled time, that would be an error. (i.e. we would want to be notified that the file is missing so that we can make it available and rerun the task.)