Multibot means more robots work at the same time to finish work faster. If BotA is busy but BotB needs to start quickly just give Bot B its own queue or mark its items urgent so it runs immediately.
This way Bot b doesnt wait for Bot a as long as both have their own robot runtimes or machines.
Basically multiple bot architecture we can work with More than one Robot on the same business process in parallel to finish the work faster.You can split the work into Queue Items and assign multiple bots to process them at the same time.
If any shared resources are used then we need to use lockign mecahnism like say we are modifying asset or modifying items on sharepoint etc we need to make sure only one bot edits it at one time
No local files are to be used (if used should be for temporary purpose)
using queue makes more sense as allocation is taken care of there
if sending mails make sure you doint send multiple times as it runs multiple times
So if we keep these in mind then any bot can run at the same time.. there wont be any issues..its more like running same process in multiple systems at same time
The idea is to run multiple robots in parallel so that work is not delayed by one bot waiting for another to finish. Each bot is connected to Orchestrator, which manages queues and distributes items.
For eg:, imagine you have two different sets of work: invoices and customer tickets. Bot A is the performer bot assigned to process invoices from Queue A. While Bot A is busy working through those invoice items, new customer tickets arrive in Queue B. Instead of waiting for Bot A to complete all invoices, Bot B can immediately start processing the customer tickets from Queue B at the same time. This parallel execution ensures that both types of work are handled simultaneously, reducing overall processing time and improving efficiency
You can simply create a queue trigger , select process (performer) to trigger, then scroll down, select which machines you want to trigger (select your 2 machines here)