I am trying to build a work flow where the job will execute tasks by name rather than by order. The goal is to have the scheduled task job execute a batch file. Then, another task will read the content of the log file to determine if an error occurred. If an error is discovered, then an email message will be sent to designated support staff.

Currently, I'm working on the task of reading the log file. If the log file cannot be found, then an error is written to the log file. The task which writes the error to the log file is not active. Despite not being active, the VisualCron job executes this task. I'm not sure if the job is misconfigured or if there is a bug.

Thanks,

John

How do you reference the inactive Task. Though Flow? Through Job/Task control Task? Or?

---

The inactive task executes if it is not referenced by the prior task. The task order is as follows:
Execute batch file task (Not used yet)
Check Batch Log File for Existence task (I'm starting here)
Read Batch Log File into Standard Output task (Called if Check Batch Log File for Existence has a return code of 0).
Scan Standard Output for Errors task (Called if Read Batch Log File into Standard Output has a return code of 0).
ERROR: Write Batch Log File does not Exist to Task Log File task (Called if Check Batch Log File for Existence has a return code of 77777. This task executes each time I run the job. This task executes after the Read Batch Log File into Standard Output successfully completes. The Read Batch Log File into Standard Output does not reference the ERROR: Write Batch Log File does not Exist to the Log File task.

I uploaded some screen shots to help explain the job. I hope this makes sense.
Thanks,

John

I just realized that the screen print I sent you shows the task enabled. I disabled the task and ran again. The screen print I am uploading shows the task executed even though it was disabled.

Thanks,

John

Hi,

I was wondering if you have any advise on how I can get around the issue?

Thanks,

John

I am not sure I follow 100% but a usual setup would be to, instead of deactivate a Task, use Flow to jump over Tasks or stop before executing if a Variable is a certain value. You have both on success where you can control which the next Task should be depending on result and then you have On start where you can check a value before a Task is being run.

---

I see there are new posts where other users encountering workflow issues with Version 8.2.6. I may downgrade to Version 8.2.5 to see if the workflow issues go away.
Thanks,
John

Hi,

we have done some fixes here: http://www.visualcron.co....aspx?g=posts&t=7249 

---

Try and clone the job, deactivate the origional one, if that works upgrade to version 8.2.7

Upgrading to Version 8.2.7 solved the issues.

Thank you,

John
😁