Sheduler & Extra

[annukka]

​We have a process which uses Extra! X-treme 9.5 / Micro Focus.
We can run it manually succefully but if we try to run it via Scheduler it doesn't work at all: it might go through a couple of steps or 1 round, and if it manage to do something: it takes minutes to Write one Value or Navigate (for example use Action Global Send Keys to send Enter ("@E@).

Any suggestions how to solve the issue ? Has anyone else faced the same problem ?

------------------------------
anna-maija elonen
------------------------------

[david.l.morris]

Can you confirm what you mean by 'manually'? There should be no difference when Scheduler starts a process and when you do an ad-hoc run in Control Room by dragging and dropping a process onto a resource and then starting it. That is, there should be no difference in performance. There certainly can be other differences as far as the process working at all or the timing or permissions and such.

------------------------------
Dave Morris
3Ci @ Southern Company
Atlanta, GA
------------------------------

[KaranSareen]

You can go to the 'Recent Activity' tab in the Control Panel and check the reference of any scheduled activity there. Also, if the schedule doesn't run at all then you can check if there is any pending session that is stopping the schedule to run.

------------------------------
Karan Sareen
Solution Support Engineer
Blueprism

------------------------------

[annukka]

By 'manually' I mean I start the process from Studio without Control Room. That way it will process all the cases in Queue without problems.
If I run it via Scheduller it will start ok, but then it will be very slow and eventually nothing happens.

------------------------------
anna-maija elonen
------------------------------

[BimalSebastian]

Hi Anna,

When you run a process from the process studio, you are basically using the client to directly initiate process, while when the process is triggered by scheduler, the app server triggers the process and it executes in the Run Time resource.
With that background, can you let us know there are any difference between the machine where you are executing from process studio and the Run Time resource. The differences could be machine specs, proximity to the end application you are automating, network differences between them....etc.

Typically, if the end application that is being automated has slower response times or if the run time resource is under sized as compared to the Interactive client, you might notice such a behavior. Hence, it is always recommended to mirror the Interactive client and Run time resources.

Thanks,
Bimal

------------------------------
Bimal Sebastian
Consultant
Blueprism
Asia/Kolkata
------------------------------