We have a job with a loop. The loop executes one sp TASK which returns either a 1 or 0. A notification is run to set var1 to PrevTask(StdOut). The JOB sets the var1 initially to 1 which allows the Loop to initiate. When the looping [every 30 seconds, for 1000 iterations] TASK returns 0, the Loop completes and the JOB continues to the next TASK that follows the Looped TASK. We have many JOBs set up like this, and we are enjoying performance as expected. Although, one JOB is not operating as expected, the Loop in this JOB was initiated as usual, the Loop began, and the sp executed and returned 0; the loop should have exited but it did not and we cannot determine why; we have checked and rechecked all variables and notifications. Using the VC client we manually stopped the JOB because we realized the action it was performing had actually completed, BUT it does not want to stop, none of the TASKs are running, yet the JOB in the VC Client GUI is reporting 'Running' status.

We have recycled the VisualCron service, thinking it would change the JOB status to 'waiting'; it did not. What is going on here, do we have an index corrupted?

Resetting the JOB took care of the situation. Status is now 'Not Run Yet'. Case closed. Thanks.

Thanks for the update!

---