"Job - Stop Job" - Status of Job is still "running" - VisualCron - Forum

Community forum

snafusmurf
2011-06-20T08:59:01Z
Hi,
many of our jobs here have "Job - Stop Job" as a task - applied to the job itself (due to error / process-handling/monitoring).
Until 5.7.5 this set the status of the stopped job to "successful" - now it still is "running", with the task that ends the job itself in this status.
Any way to turn this off?

BR & thx
Support
2011-06-20T09:01:29Z
What kind of Task is just hanging in "Running"?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
snafusmurf
2011-06-20T09:04:33Z
Support
2011-06-20T09:06:12Z
Ok, thanks, we will investigate and get back to you ASAP.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
snafusmurf
2011-06-20T09:07:23Z
to explain this a little, most of our tasks are like this:

a. call stored procedure on our oracle-server that flgs the job as "running"
b. do something
b1. on error: goto e
c. call stored procedure that flags job as success
d. END JOB <-- this is where the job is still "running"
e. call stored procedure that stores error-msg etc.
Support
2011-06-20T09:52:02Z
We can't seem to reproduce with the Stop Task alone. I don't see the exact flow in your description:

1. Where does the Stop Task come in?
2. Are we talking about the same VisualCron Job/Task Control: Stop Task?
3. What Task is the Stop Task trying to stop?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
snafusmurf
2011-06-20T10:04:28Z
Originally Posted by: Support 

We can't seem to reproduce with the Stop Task alone. I don't see the exact flow in your description:

1. Where does the Stop Task come in?
2. Are we talking about the same VisualCron Job/Task Control: Stop Task?
3. What Task is the Stop Task trying to stop?



ad 1: (this is the general flow of our simple-standart-jobs)
a. call stored procedure on our oracle-server that flgs the job as "running"
b. do something (update some tables/fetch files/...)
b1. on error: goto e
c. call stored procedure that flags job as success
d. END JOB <-- HERE IS THE STOP-TASK ("job - stop job", it tries to stop the whole job so "e." is not reached!)
e. call stored procedure that stores error-msg etc.

ad 2:
nah, it is the "job - stop job" - task

and

ad 3: the "stop-job"-task is trying to stop the job it is running in (the job tries to end itself with this task)
Support
2011-06-20T10:25:15Z
So, why are you trying to Stop Job instead just set the first "On error" Stop Job?

The Stop Job task was not designed to stop itself but I see no reason to use it.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
snafusmurf
2011-06-20T11:51:43Z
Hmm, first of all - since every job calls the same procedure but with different parameters, integrating the call in the job seemed easier at the time i set the jobs up.
furthermore i now *have* several hundred jobs that worked fine untill the update to 5.7.5, but stopped doing so - and if it can be avoided I wouldn't want to change them all.
It seems unlogical to me to have a job still "running" that has been stopped - regardless by wich job.
If the task "stop job" wasn't intended to stop the job it is part of - why not grey it out?
snafusmurf
2011-06-20T11:53:29Z
Ah, sorry - I think I misunderstood you post - I do not stop the job on the error because I am actually *doing* something after the error - writing the error-message in our task-tracking-db and such.
Support
2011-06-20T11:56:26Z
You call the stop Job but you are not stopping the Job? If stop Job worked as it was supposed to the Task after Stop Job should not be run. But perhaps you are saying that you have Tasks in the Stop Job Job that do things after it has stopped the Job?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
snafusmurf
2011-06-20T12:09:27Z
I actually think the job stopped - it just does not show in the job's status!
The tasks after the stop-job are NOT started - but the stop-task itself seems to be still running!
snafusmurf
2011-06-20T12:30:29Z
Jobs that are triggered on completion of the not-completely-stopped job are not starting up either.
Support
2011-06-20T14:21:26Z
Ok - the problem is the new addition of "Run synchrous" option. With that on (checked), on the Stop Job it will hang. Because it is trying to wait for result while it is still running.

What you need to do is to uncheck that. The problem is that, in your version, the "uncheck" might be disabled. We have enabled this for next version.

If you don't plan to run any follow up Tasks I recommend that you change to "On error"->Stop Job instead. That is more efficient.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
snafusmurf
2011-06-20T15:54:48Z
hmm, any idea how fast this will change back to the old version?

:)

Support
2011-06-21T07:09:26Z
Either you go one version back or you wait for the new beta which will probably be released in the weekend.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2011-06-23T14:24:08Z
The beta (with the fix) is released here:

http://www.visualcron.co....aspx?g=posts&t=1851 
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top