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


hawkings
2010-09-23T12:39:14Z
When starting a job with the "Job/Task Control" task, the job is started without conditions.

This sounds like a bug.

Best regards,
René
Sponsor
Forum information
ErikC
2010-09-23T13:03:43Z
I think it is the way you look at it.
You could also put conditions to the task telling to run the job.

But, you might be right...

Regards,
Erik
Uses Visualcron since 2006.
hawkings
2010-09-23T13:07:32Z
You mean, I could instead of using the "Job/Task Control" task to start a new job, instead use a condition to do this?
Support
2010-09-23T13:30:26Z
Perhaps you are not selecting Run Job->With Conditions if you run it manually?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
hawkings
2010-09-23T13:33:11Z
No no, I can see I haven't made myself clear. Sorry

I have added a "Job/Task Control" task to Job A, which supposedly was to start Job B.
However - it starts Job B without conditions, which means that all the conditions in Job B are ignored.
ErikC
2010-09-23T13:38:28Z
What I meant was that you can re-use the condition used on your job for your run job task.

Regards
Erik
Uses Visualcron since 2006.
hawkings
2010-09-23T13:48:20Z
Sorry Erik, I tried, but I am not sure I can decipher your point. :-)
In the above example with Job A and Job B I don't use conditions to start/iterate jobs, so there is nothing to "re-use". I just have a "Job/Task Control"-task to start Job B.

I apologize for being dense.
ErikC
2010-09-23T14:12:21Z
Ohh, so conditions to tasks in Job B are not working when you run it from a task in job A?

If that's the case, it's not the way it should be.

Regards
Erik
Uses Visualcron since 2006.
Scroll to Top