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


Support
2009-03-26T20:10:13Z
Changes in 5.0.7

[BUGFIX] Server: Fixed a problem with Copy files Task
[BUGFIX] Client: Changed to SaveFileDialog from OpenFileDialog in Export settings Task
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Sponsor
Forum information
hawkings
2009-03-27T08:54:25Z
Hi Henrik.

I wrote you regarding the bug within conditions, when the condition tries to start a task within the same job.
Did you have time to look into this bug?

I can add the information:

It fails: If the condition is set to start a disabled task within the same job
It succeeds: If the condition is set to start a disabled task in another job
It goes into a loop: If the conditions is set to start a enabled task within the same job

This was tested with 5.0.5, and I haven't bother try with 5.0.7, since the bugfix list didn't reveal any change regarding to this issue.

Best regards,
René Truelsen
Support
2009-03-27T12:12:35Z
We will look at this. But the behaviour should be that a Task can never be run if it is disabled. So the bug lies in where it succeeds, it should not succeed to start the disabled Task.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
hawkings
2009-03-27T12:37:24Z
Why should it not be allowed to start a disabled task?
For me a disabled task is a task that is not run as a part of the regular job. But it can be useful to have a task that should be executed alone and not as a part of the job, for example a notification task. An example would be:

task a) download files from ftp
condition b) if number of downloaded < 1 then run task c) else continue
task b) rename downloaded files
disabled task c) send emails that notifies that number of downloaded < 1

In this case you only want task c to be run if condition b) is fulfilled, and thus should not be executed as a part of the regular "Start Job".

Best regards,
René
Support
2009-03-27T13:00:44Z
Task status (active/inactive) are not constructed to control the flow. If they are used like that there could be great risks associated. For example, if one adminstrator immidiately want to stop all further execution but a Condition overrides this.

Conditions can already do what you want to do without working with disabled Tasks. In the Condition action you just set it to exit the Job or jump to another Task after the Task you don't want to run.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
ErikC
2009-03-27T13:20:04Z
I agree, a disabled task should never run.

Regards
Erik
Uses Visualcron since 2006.
jmb
2009-03-30T12:52:05Z
with new forum, impossible to download setup
Support
2009-03-30T12:53:58Z
Erik, can you download? I could download it.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
GrahamG
2009-03-30T13:15:37Z
Hi Support,

The beta download doesn't work for me either. It's o.k. for the released version from the "Download" page.

Graham
Support
2009-03-30T13:18:05Z
What happens when you try to download it?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Support
2009-03-30T13:25:41Z
It was a permissions issue. Should be ok now.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
GrahamG
2009-03-30T13:35:16Z
jmb
2009-03-30T13:44:00Z
ErikC
2009-03-30T20:19:05Z
Support wrote:

Erik, can you download? I could download it.


Yes, I'm able to download the beta.

Regards
Erik
Uses Visualcron since 2006.
levi
2009-03-31T00:07:54Z
Henrik,

This has fixed my file/folder copy! Thanks!

Levi.
Support
2009-03-31T10:16:57Z
Thanks for the feedback.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Users browsing this topic
Scroll to Top