I have a job set up with three tasks. Task one fires an executable that creates a .csv file. Task two FTPs the file to a client. Task three saves the file to a backup directory, deleting the original.

All three tasks complete successfully, with no errors in the log, but the job itself fails, generating a "failure" notification email (set at the job level). There are no errors in the log at the job level, either. External to VC, I can also confirm that the file has been created, FTPed to the client's server, and backed up, just as it should.

This job is basically identical to 15-20 other jobs we have set up that do the same thing, but for different clients. All the other jobs work.

Any suggestions?

Thanx muchly

What does the logfile say? You can find this log in the application folder of visualcron and in a subfolder called 'Log'.

Regards,
Erik

---

Thanks for that. I didn't know where/whether VC logged this info. The client GUI task log only covers very recent events.

The last couple of times the job failed, the error was in the FTP task. I have all three tasks set up to re-run up to three times if they fail. Apparently, this client's FTP server is only intermittently available for some reason (probably overtaxed). First attempt fails, then second (or third) attempt succeeds ... the job completes all tasks, but still acts as though it failed.

Now, I've seen a thread or three discussing how to get a job to only fire off a "failure" notification if all repeated attempts fail, but I didn't see any clear answer on whether this is possible (or how to set it up) in VC.

Can anyone point me to a thread answering this question?

You may have set the Notification at Task level instead of Job level. Because it will fail at the Task once (and send email if you have a Notification). It will, however not, fail on Job level.

---

The notification is definitely set at the job level; no notifications set at task level anywhere ... and nevertheless, according to the log, FTP task failed the first time, succeeded the second time, and the job threw a failure notification.

Note, however, we are running an older version of VC ... 5.3.2. Looks like that is about a year old. Has the notification behavior been changed within the past year?

Yes, this has most probably been fixed after that.

---

Maybe you can verify that on another server which don't have VisualCron before upgrading?

---