Hi

I have a question on the order of execution for multiple tasks and notifications in a job. In my scenario I have a job with with two tasks: TaskA & TaskB
with a SQL notification connected to TaskA. The job is configured to run tasks in order: TaskA first then TaskB. The majority of the time the execution
is as follows:

1) TaskA
2) SQL notification TaskA
3) TaskB

However, every once in awhile the execution does the following:

1) TaskA
2) TaskB
3) SQL notification TaskA

I have verified the two cases happen from the VisualCron logs. My question is what is the behavior suppost to be? Normally this wouldn't be a problem
except that TaskB uses the results of the SQL notification, hence if the notification happens after TaskB is already started, it doesn't have any results
to work with. I was running v4.9.21 and then upgraded to v4.9.40 but both display this behavior. I am also setting up the job via the API but I don't think
that has anything to do with the behavior.

I didn't think this question was going to discombobulate anybody overthere...Anybody going to answer this one or is it going to become a smelly fish in the forum?

Missed this one. Sorry. It seems very strange. When looking at the log file do you have different timestamps? I was just thinking that it happens within the same second and that the events are just sorted that way.

---

Attached is a snippet of the log file showing the problem, there are different timestamps. I do have a scenario where I can reproduce the problem
now which is to reboot the machine running VisualCron and then run the job. The 1st time the job runs(JOB1) the problem shows up, the 2nd time the job
runs(JOB2) the sql notification(task complete) runs before the 2nd task runs which is the way I thought is should work.

12/16/2008 11:15:44 AM Comm IN: SERVERSETTINGSREQ
12/16/2008 11:15:44 AM Comm IN: LICENSEREQ
12/16/2008 11:15:44 AM Info User "VisualCron Default Admin" - Added Notification (cdde40cd-6e33-476a-ac8e-a286c21b3586)
12/16/2008 11:15:45 AM Debug Saving Notifications
12/16/2008 11:15:45 AM Info Job added
12/16/2008 11:15:45 AM Debug Saving Jobs
12/16/2008 11:15:46 AM Info User "VisualCron Default Admin" - Added Job: JOB1
12/16/2008 11:15:47 AM Info Job started: JOB1
12/16/2008 11:15:47 AM Info User "VisualCron Default Admin" - Ran Job: JOB1
12/16/2008 11:15:48 AM Info Task started: CALC
12/16/2008 11:15:55 AM Debug Process status - About to raise TaskCompleted (1)

12/16/2008 11:15:55 AM Info Task completed: CALC
12/16/2008 11:15:56 AM Info Task started: NOTEPAD
12/16/2008 11:15:57 AM Debug Running SQL Notification: ''

12/16/2008 11:16:01 AM Debug Process status - About to raise TaskCompleted (2)
12/16/2008 11:16:01 AM Info Task completed: NOTEPAD
12/16/2008 11:16:01 AM Info Job deleted
12/16/2008 11:16:01 AM Info Job completed: JOB1
12/16/2008 11:16:07 AM Debug New client connected.
12/16/2008 11:16:07 AM Debug Client: 15c09e1e-1c40-4a1d-91bf-d45b7b559094 (192.168.168.52) has disconnected
12/16/2008 11:16:07 AM Info User "VisualCron Default Admin" - Logged in succesfully through Socket (39d2565f-85fa-4477-bfac-aaf764d15f4e)
12/16/2008 11:16:07 AM Debug Updating login status for: 39d2565f-85fa-4477-bfac-aaf764d15f4e
12/16/2008 11:16:07 AM Comm IN: SERVERSETTINGSREQ
12/16/2008 11:16:07 AM Comm IN: LICENSEREQ
12/16/2008 11:16:07 AM Info User "VisualCron Default Admin" - Added Notification (70f4d45d-2b48-4879-ba8e-5b234c67dc40)
12/16/2008 11:16:07 AM Debug Saving Notifications
12/16/2008 11:16:07 AM Info Job added
12/16/2008 11:16:07 AM Debug Saving Jobs
12/16/2008 11:16:07 AM Info User "VisualCron Default Admin" - Added Job: JOB2
12/16/2008 11:16:08 AM Info Job started: JOB2
12/16/2008 11:16:08 AM Info User "VisualCron Default Admin" - Ran Job: JOB2
12/16/2008 11:16:08 AM Info Task started: CALC
12/16/2008 11:16:15 AM Debug Process status - About to raise TaskCompleted (3)

12/16/2008 11:16:15 AM Info Task completed: CALC
12/16/2008 11:16:15 AM Debug Running SQL Notification: ''
12/16/2008 11:16:15 AM Info Task started: NOTEPAD

12/16/2008 11:16:18 AM Debug Process status - About to raise TaskCompleted (4)
12/16/2008 11:16:18 AM Info Task completed: NOTEPAD
12/16/2008 11:16:18 AM Info Job process was aborted by user.
12/16/2008 11:16:18 AM Info Job deleted
12/16/2008 11:16:18 AM Info Job completed: JOB2
12/16/2008 11:16:58 AM Debug Saving Jobs

I have verified the two cases happen from the VisualCron logs. My question is what is the behavior suppost to be? Normally this wouldn't be a problem
except that TaskB uses the results of the SQL notification, hence if the notification happens after TaskB is already started, it doesn't have any results
to work with. I was running v4.9.21 and then upgraded to v4.9.40 but both display this behavior. I am also setting up the job via the API but I don't think
that has anything to do with the behavior.

Just out of curiosity what happens when you add a wait "x" seconds task in between TaskA and TaskB? Do the tasks still have this issue?

I need to correct myself after investigating this. Notifications are run in a new separate thread. There is no sequential act and theoretically the next Task could be run before the Notification set on the first Task. If you need the Notification being run sequentially you should use an Email or SQL Task instead.

---