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


Guest
2011-07-05T12:21:10Z
Visual Cron 5.7.5

A Job with two Tasks. Timeout set to one minute. If we take a look at the Job log, we find successful finished jobs with runtime of 317.0sec?! How can this be?

We see this behaviour also with timeout settings on Tasks. Set to a few secounds. Successful finished tasks, with longer runtimes.
Sponsor
Forum information
ErikC
2011-07-05T13:12:54Z
Hi Laminar,

What kind of task types are you using in the mentioned job?

Regards,
Erik
Uses Visualcron since 2006.
Guest
2011-07-05T14:04:24Z
Hi Eric,
this is one of the Jobs:

See the spoiler for the job code:
ErikC
2011-07-05T17:27:20Z
Hi,

I think it is easier to tell what the custom setting are than posting the whole job info from the job configuration file.

Regards
Erik
Uses Visualcron since 2006.
Guest
2011-07-06T05:30:10Z
Hi Erik

I understand, I would have done it differently if I know how. Nevertheless, what else do you need to know to give me any help to solve my issue?

As you, at least, can see out of the jobs definition it is an 'execute' task. Which executes vb-script
Thats most of our task. Cmd-Batch, VB-Script, FTP and HTTP
Have you heard or see of any other users such behaviour of VisualCron?

greetings
Marcel
ErikC
2011-07-06T06:15:12Z
Please check the 'Extended debug logging' at the server settings.
Run the job again and look at the log file in the log dir of the visualcron application.

Location of the file:
[appdir]\log\log_server[yyymmdd].txt

Please place the part of your job in this forum.

Regards,
Erik
Uses Visualcron since 2006.
Scroll to Top