I have a process which handles 1000 plus queue based transactions. A dispatcher adds all the items into a single queue. I have 4 bots available at all times to process from the queue, how will i configure these bots in the orchestrator
Hi @Sachin_Sreekumar here are the steps to run Multi-bot Architecture:
1. Queue Setup
- Create one Queue in Orchestrator (say
Process_Transactions). - Your Dispatcher process adds all 1000+ items into this queue.
2. Performer Setup
- Deploy your Performer process (the one that fetches and processes queue items) to the environment/modern folder where all 4 bots exist.
- The Performer should use the Get Transaction Item activity → Orchestrator automatically ensures that each queue item is locked and picked by only one bot.
3. Job/Trigger Configuration
- Create a Queue Trigger to run the Performer.
- Queue Trigger: Configure it on your queue → when new items are added, Orchestrator will automatically start jobs for the Performer.
- Max Concurrency: Set it to 4 (since you have 4 bots). This ensures Orchestrator will start up to 4 jobs of your Performer process in parallel.
Regards,
Akash Javalekar
Create two triggers first a time based for your dispatcher and run it on specific machine and bot as you need
Then use a queue trigger and all the available machines and robots (that is 4) to the folder and set max jobs as 4 so that once items are added all 4 bota gets triggered with available items
Cheers
Thanks. Suppose the number of transactions are very random, like it can be 10 or it can be even 10000 in some cases and there are 10 bots available. What will be the best way to approach this situation
1 Like
The approach remains same..if you have more bota available then increase the job count in queue triggers
And for 10 items if you dont want more bota there there is an option to control after how many new otems next bot ahpuld atart you can use that as well
Cheers
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.