Running Blue Prism 24x7

[RupanjalBhowmi1]

I have a process where request comes throughout the day. Should I schedule for 24x7 or is there a way to trigger the Bot based on some event.

[John__Carter]

A better option is to run 23:55x7, if you run 24x7 you'll create a giant session log that will be difficult to archive later. Aside from calling a process as a web service, or using the command line to start a process, you have to have a process running that 'listens' for the event, whether it's a file drop, email, 3rd party DB update or work queue item. There are a number of design patterns to try, so maybe work with the Lead Dev in your organisation to try different ideas. Alternatively try your delivery partner company or your BP representative.

[syed.viqar.raza]

Hi John, with regards to Archiving, does this issue occurs (if you run 24x7 you'll create a giant session log that will be difficult to archive later) even if we set Auto-Archiving? Kindly advise.

[Mei_YingLim]

By 23:55x7 are you referring to a 5 minute rest in the day for the ""listening"" bots?

[John__Carter]

Syed - yes, archiving won't remove logs from a running process, so it won't prevent a mega-log when a process runs 24x7. limmeiying - what I'm saying is to make the processes 'take a coffee break' to limit the size of the logs. The resource PC can run 24x7.

[TomCirone]

If you don't want to have the 5-minute downtime of  23:55x7 you can also calculate the start time when you first start the process (before you start the loop).  Then at every loop you check if it's been running for 24 hours, at which point you stop the run.  Then you schedule the process to run every minute (it will only actually run when it isn't currently running). This will also cause the process to start running right away if it terminates for any reason, which could be a pro or a con.