Has anyone got a process running 24 x 7 in the operational environment? Have you encountered any issues in this approach? If so, what were they and how did you resolve them?
Hi Tim
Got a process running in a hospital 24x7. Occasionally it falls over and has to be restarted but apart from that has been running pretty non stop for 4 months.
In theory you could run a process all the time and Blue Prism has the odd customer that does.
The problem with this is that you won’t see the session by default in Control Room as it by default shows today's sessions. You’d need to filter the list every time you wanted to check on the process.
Also you run the risk of gigantic log files.
Using the scheduler allows Blue Prism to restart the process in the event of failure. You can have numerous tasks to restart sessions for each iteration of the scheduler. This wouldn't be possible running a process continually unless you set up hundreds or thousands of tasks or create a task loop which is not advisable as any persistent failure for whatever reason will fill up the DB very quickly.
A better approach is to run processes nearly 24/7. For example have the scheduler start the process each day at 6am but have the process finish at 5:55am in time for the next schedule to start it off again.
Using your approach Chris (in your last comment), where multiple resource PC’s are being used the down time can be scheduled in such a way so that the process is always running on at least one machine.
