29-06-19 08:54 AM
23-12-20 09:40 AM
Hi Peter,
do you mind sharing some info around how to setup the shell script? We are too facing similar issues with schedules going into a pending state
thanks
varun
23-12-20 09:47 AM
Hi Nicholas,
when you say external scheduler, do you mean windows scheduler? How are you triggering the next process on completion?
thank you
varun
23-12-20 11:07 AM
23-12-20 01:06 PM
Hi Team,
Please Check your Licence session because if incase all your instance in Bp is used/Busy then sometimes Your Schedule process will be in pending state and not get triggered into Running.
So just to make sure please check when your process went into pending was there any bandwidth available at that moment.
Regards,
Manoj
23-12-20 02:47 PM
Hi,
In my experience the license check occurs before the process is taken to the pending state. It should not be possible to have a pending session if all licenses are taken.
peter
23-12-20 02:52 PM
I built a small custom scheduler that runs as a windows service. When the scheduled time is hit, it logs a request in SQL table which is picked up by a custom controller service, which then kicks it out to an available robot via the automatec.exe command line.
As far as triggering the next process in the chain, the controller service monitors work queues and has triggers set up to launch processes when either a work queue has finished all its items, or has finished items with specific key values.
Both services are custom solutions but it has worked out very well for us. To my original point, the only time I've seen the automatec.exe command line fail to launch a process is in the presence of heavy network loss. It does make me curious how automatec.exe is launching processes without issues, whereas Blue Prism scheduler was getting stuff stuck in pending quite frequently.
04-01-21 06:46 AM
04-01-21 06:48 AM
18-06-21 04:25 PM
07-07-21 10:55 AM