We have a server which has recently been upgraded from 4.9.3 to 4.9.40.

On the old version we had a condition that checked the result of the previous task using the "Auto (previous Task or Job)" option. This condition was deployed on most tasks in most jobs and worked OK. The new version has introduced the "On Error" tab for tasks which duplicates our condition. We haven't yet got around to removing the condition from all of the tasks.

We are experiencing problems with the first task (or two) in a job running and finishing successfully but the other tasks not running. There is nothing in the log to suggest why they didn't run: although, strangely, on one job were the last task is inactive there is an entry saying the task has been skipped due to it being inactive.

Removing the condition seems to fix the problem so we are going to do that but we're wondering why this should be happening.

I have attached the log entries for one such job (not the one with the deactivated task). There are four tasks the first one has run successfully but none of the other three seems to have even tried to start.

I suggest you go to the Condition and log tab. Check debug log and you will see in the Log window why and how the flow really is when you run the Task.

---

I have run a test job with the debug option and got the following (also attaching an export of the relevant job and condition)

15/05/2009 14:48:27 Karls test job Job completed: Karls test job
15/05/2009 14:48:27 Karls test job Next execution (2) for job 'Karls test job' is: 00:00:00
15/05/2009 14:48:27 Karls test job Job (498) was removed from processlist: Karls test job
15/05/2009 14:48:27 Karls test job Pause for thought Condition Set (Task) returned: MatchError-> ActionExit
15/05/2009 14:48:27 Karls test job Pause for thought Running Condition Set: 'Check if previous task ran OK' for Task: Pause for thought
15/05/2009 14:48:27 Karls test job Make dir Task (1495) was removed from processlist: Make dir
15/05/2009 14:48:27 Karls test job Make dir Process status - About to RemoveTaskProcess (1495)
15/05/2009 14:48:27 Karls test job Make dir Process status - About to SendTaskProcess (1495)
15/05/2009 14:48:27 Karls test job Make dir Setting previous task in TaskProcessCompleted: Make dir (6f9ed921-38f1-450a-9196-3181af1dc93b) in job: Karls test job
15/05/2009 14:48:27 Karls test job Make dir Task completed: Make dir
15/05/2009 14:48:27 Karls test job Make dir Task started: Make dir
15/05/2009 14:48:27 Karls test job Make dir Task (1495) was added to processlist: Make dir
15/05/2009 14:48:27 Karls test job User "VisualCron Default Admin" - Ran Job: Karls test job
15/05/2009 14:48:27 Karls test job Job (498) was added to processlist: Karls test job
15/05/2009 14:48:27 Karls test job Job started: Karls test job

The problem is here:

Pause for thought Condition Set (Task) returned: MatchError-> ActionExit

I am not sure what this Condition tries to do but perhaps you are referencing to a file or task that does not exist.

---

The problem is here:

Pause for thought Condition Set (Task) returned: MatchError-> ActionExit

I am not sure what this Condition tries to do but perhaps you are referencing to a file or task that does not exist.

Sorry for the delay in replying I have been on holiday😁.

The condition is checking the result of the previous task - not a specific named task but the "Auto (previous Task or Job)" option. This worked prior to the upgrade but now seems to clash with the new 'On Error' functionality.

Export of the condition is as follows:

- <ArrayOfConditionSetClass xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
- <ConditionSetClass>
- <Conditions>
- <ConditionClass>
<ConditionType>VisualCron</ConditionType>
- <CVisualCron>
<LocatorType>Auto</LocatorType>
<CheckType>TaskExitCodeIs</CheckType>
<MatchType>MatchIs</MatchType>
<JobId />
<TaskId />
<ExitCode>0</ExitCode>
<Contains />
</CVisualCron>
<Id>867988b1-ecbf-4449-9070-1537ae2f1256</Id>
<SetId>74da0b4a-b8a8-4333-9c2b-61afccefa144</SetId>
<Active>false</Active>
<Description>Check if previous task ran OK</Description>
</ConditionClass>
</Conditions>
- <ActionMatchAll>
<ActionType>ActionContinue</ActionType>
<WaitType>NoWait</WaitType>
<WaitHours>0</WaitHours>
<WaitMinutes>0</WaitMinutes>
<WaitSeconds>0</WaitSeconds>
<JobId />
<TaskId />
</ActionMatchAll>
- <ActionMatchAny>
<ActionType>ActionContinue</ActionType>
<WaitType>NoWait</WaitType>
<WaitHours>0</WaitHours>
<WaitMinutes>0</WaitMinutes>
<WaitSeconds>0</WaitSeconds>
<JobId />
<TaskId />
</ActionMatchAny>
- <ActionMatchNone>
<ActionType>ActionExit</ActionType>
<WaitType>NoWait</WaitType>
<WaitHours>0</WaitHours>
<WaitMinutes>0</WaitMinutes>
<WaitSeconds>0</WaitSeconds>
<JobId />
<TaskId />
</ActionMatchNone>
- <ActionMatchError>
<ActionType>ActionExit</ActionType>
<WaitType>NoWait</WaitType>
<WaitHours>0</WaitHours>
<WaitMinutes>0</WaitMinutes>
<WaitSeconds>0</WaitSeconds>
<JobId />
<TaskId />
</ActionMatchError>
<Id>74da0b4a-b8a8-4333-9c2b-61afccefa144</Id>
<Description>Check if previous task ran OK</Description>
<ExtendedLogging>true</ExtendedLogging>
</ConditionSetClass>
</ArrayOfConditionSetClass>

The difference is that we now have the default setting "Stop" if a Task has failed. If you want to use it as before you should set it to "Continue".

---

The difference is that we now have the default setting "Stop" if a Task has failed. If you want to use it as before you should set it to "Continue".

Yes, we had noticed that!

What we have though is a situation where we have two tasks, let's call them A and B.

Task A runs first and has the stop job on fail option set.

Task B runs after task A and has a condition which means it only runs if A is successful.

If task A is NOT successful then the job should stop and the condition is not tested.

If task A is successful then the job should continue and the condition should allow task B to run.

What actually seems to happen when task A is successful is that the job continues but the condition prevents task B starting. It's as if either the condition isn't working correctly or the result of task A is not right in someway. Task A says it worked OK, the failure action says task A was OK so the job continues but when task B's condition checks task A's status it finds it to not be OK.

Before we begin a deeper investigation it would be interesting if you turned logging on the Condition. When logging is added at Condition Set you will see in the normal log why and which path it took. Please do that and come back if this still does not make anything more clear.

If so, paste the log output of the Condition set.

---