https://community.blueprism.com/t5/Product-Forum/Schedule-v-Process/m-p/89297#M39706 Hi Graeme, I think an important factor to consider which approach to use would be the number of licenses available to run robots concurrently. If the sleep time is not small, it would be a good option to use the scheduler. However, if you need to keep checking the queues quite frequently (such as every 5 or 10 minutes), then it makes sense to use the wait in the process rather than triggering a new process. Wed, 28 Jun 2017 12:42:00 GMT ShreyansNahar1 2017-06-28T12:42:00Z https://community.blueprism.com/t5/Product-Forum/Schedule-v-Process/m-p/89296#M39705 Hi, We have several processes that we need to run constantly during the day - the queue they process being populated by other processes throughout the day. Some we have built, so they stop when the queue is empty and have the schedule set to run the process every 5 minutes. Others we have built, so the process does the wait, before re-checking the queue (i.e. it is only scheduled once, but runs all day). Just wondered what Blue Prisms recommendation was, as to which solution was better. Tue, 27 Jun 2017 13:43:00 GMT https://community.blueprism.com/t5/Product-Forum/Schedule-v-Process/m-p/89296#M39705 Graeme__Tacon 2017-06-27T13:43:00Z https://community.blueprism.com/t5/Product-Forum/Schedule-v-Process/m-p/89297#M39706 Hi Graeme, I think an important factor to consider which approach to use would be the number of licenses available to run robots concurrently. If the sleep time is not small, it would be a good option to use the scheduler. However, if you need to keep checking the queues quite frequently (such as every 5 or 10 minutes), then it makes sense to use the wait in the process rather than triggering a new process. Wed, 28 Jun 2017 12:42:00 GMT https://community.blueprism.com/t5/Product-Forum/Schedule-v-Process/m-p/89297#M39706 ShreyansNahar1 2017-06-28T12:42:00Z