RoboTask forum

I have RoboTask 2.6 running on a machine which has most of the time almost 100% cpu load.I start a script cyclic with that Cyclic Triggering Event set to start every 3600 sec (which is 60 minutes).The problem is, the script does not start every 60 mins. Sometimes it starts after 150 mins, sometimes after 200 mins and sometimes it starts never.Any suggestions?

Maybe your computer was loaded by high-priority processes. RoboTask have normal priority as most applications. In this case the system doesn't give to RoboTask enough processor resources.
Try to increase priority of RoboTask process in task manager (see processes tab). This have to solve the problem.

Thank you for the report, we'll investigate the problem. Probably it's possible to improve the algorithm.

Also tell me, please, the following information:
- How do you use RoboTask: as simple application or as NT Service
- characteristics of computer

Hi Oleg,thanks for the fast response.All processes have standard priority. There is only one process which takes the most cpu load but it has standard priority too.Now I've set the RoboTask priority to "high" and will see how it works.There was another problem which has possibly the same cause:The sript clicks a button in a program and then waits for a "confirm" button to click. Sometimes the "confirm" button appeared but was not clicked from RoboTask. Maybe RoboTask was to slow and missed the appearance of the "confirm" button.

Oleg wrote:Also tell me, please, the following information:
- How do you use RoboTask: as simple application or as NT Service
- characteristics of computer

Sorry, I forgot:- simple application- characteristics: Standard Desktop PC, AMD Athlon 2 GHz, 512 MB, W2k

The sript clicks a button in a program and then waits for a "confirm" button to click. Sometimes the "confirm" button appeared but was not clicked from RoboTask. Maybe RoboTask was to slow and missed the appearance of the "confirm" button.

It's very probably
Regarding priority: your computer may be loaded by system processes which always have high priority (for example disk operations or some other hardware oparations) These processes may brake other software processes.
We have tried to simulate this situation, but we see this effect only if we set high priority to processes, which load the system. Maybe this depends on computer configuration too.