Set job variable bug - VisualCron - Forum

Community forum

thomas
2018-11-27T16:33:44Z
Setting of job variables has changed behaviour in 8.4.1 (or maybe 8.4.0), and I'm pretty certain it's a bug causing us a lot of trouble

To reproduce the issue:

1) Create a job like in the image below. It has a job variable called 'var'. Set it to zero. Start with a task that sets it to zero (in case you are running test several times).
Then create a for loop that loops say 10 times. Increment the variable by 1 in each loop cycle. Then create a task that writes to file (or whatever you want)
Capture.PNG

2) Run the job, and it produces the correct result
Capture.PNG

3) Next, create another job that calls the job above. Do not load any variables, just leave as is. It makes no difference if you check any of the boxes below 'Job variables'
Capture.PNG
Capture.PNG

4) Run the new job. It produces this result
Capture.PNG

This cannot possibly be the intended behaviour. The child job updates the variables, but the Write file job 'remembers' the old variable
thomas
2018-11-29T07:34:43Z
Have you had a look at this? Changing the way variables work is a serious bug imo. Jobs can be triggered in 8.4.1 with the wrong parameters...
Support
2018-11-29T07:47:16Z
It has only changed for 8.4.0 but please test latest build of 8.4.1 (re-download and re-install). Thanks
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
thomas
2018-11-29T08:36:50Z
thomas
2018-11-29T12:34:21Z
Hi

It fixed the problem, but a new bug was introduced. The problem now is that it fails if jobs call each other, more than 1 level deep. If job 1 calls job 2, and job 2 calls job 3, it just hangs and stays as running forever

To reproduce (see image):

Capture.PNG

1) Create job1: It just calls Job 2, nothing else. no params
2) Create job2: It calls Job 3, with a parameter. I called it 'var' and has value 2
3)Create job3: Has job variable 'var'. It writes 'var' to output using powershell

If you run from Job2, it works, if you run from job1 it hangs.
thomas
2018-11-29T12:41:13Z
I just tested a simpler version: You can remove variables and just hardcode a value in job 3. It is unable to call a job that calls a job (nothing to do with variables)
Support
2018-11-29T12:44:04Z
Can you attach these 3 Jobs?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
thomas
2018-11-29T12:50:42Z
  NestedJobs.zip (3kb) downloaded 21 time(s).

Added jobs. Try calling from job 2 first, success, then from job 1, fail. Make sure you test on latest 8.4.1 patch, as this worked before the patch
thomas
2018-11-29T13:09:58Z
As an aside note, in the .net execute task -> references, I cannot find System.Collections.Generic or System.Linq on the server. Locally on the client they exist. So when we try to add a reference it fails (probably because they don't exist on server). We don't use this task, but it could be an issue for others.
Support
2018-11-30T07:47:51Z
Please test this build: https://www.visualcron.c....aspx?g=posts&t=9226 

(about the Job lock running issue).
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
thomas
2018-12-01T16:49:41Z
Hi

It fixed the issue, but another bug appeared. In job variables, clicking on Active gives the direct id. And all the other radio buttons are greyed out

Capture.PNG
Scroll to Top