Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


j.mason@epyx.co.uk
2013-08-14T10:36:19Z
Hi
After upgrading from 6 to 7.0.3 my sql task output notifications stopped working.

Where I use {TASK(Active,StdOut)} there is now this error in the variables viewer: "[Error in SetVar, string: {TASK(Active,StdOut)}, err: Object reference not set to an instance of an object.]"

Using {TASK(PrevTask,StdOut)} instead produces the correct result.

It looks to me as though there is an array offset type bug in the handler for task variables of type sql.
Sponsor
Forum information
Support
2013-08-14T10:53:32Z
This is a result of new Notifications are Tasks now. Because of that, Active refers to the Task Notification instead of the last run Task (PrevTask).
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
j.mason@epyx.co.uk
2013-08-14T14:08:54Z
Well if you say so ok. To me though they look like a different type of object everywhere that matters. Tasks appear under jobs. Notifications appear under notifications, and are linked to tasks. Seems not at all intuitive.
Support
2013-08-14T14:26:30Z
The reason becaus of this was that we had about 6 Notifications types that were not maintained. We had to do duplicate work if we wanted to change the Email Task and Email Notification. What we did was to let the Notification inherit from the Task object, this gave us 80 new Tasks and zero maintenance for Notifications. It is just the context that became different then.

We might change so that Active still refers to the Task that was last started but I am not sure right now.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top