i’m using two robots to treat a large mass of queues, normaly if a robot start a queue automaticly the status change from new to In Progress … but sometimes … i found out that the both robots take the same queue.
how this can be possible if the orchestrator is taking charge of this!!
ROBOT 01 :
04/21/2022 12:12:14 Mass transfer input part [INFO] Start process
04/21/2022 12:12:14 Mass transfer input part [INFO] Closing old application instances
04/21/2022 12:12:14 Mass transfer input part [INFO] Start opening applications
04/21/2022 12:12:14 PM Mass transfer input part [INFO] Recovery of GRC login credentials
04/21/2022 12:12:17 Mass transfer input part [INFO] End of application opening
04/21/2022 12:12:18 Mass transfer input part [INFO] Init draft value = False
04/21/2022 12:12:18 Mass transfer input part [INFO] Start processing next order: ID = 3457
04/21/2022 12:12:20 Mass transfer input part [INFO] Number of transfers found and accepted by ocr for this order = 27
04/21/2022 12:12:20 Mass transfer input part [INFO] Number of transfers found and rejected by ocr for this order = 0
04/21/2022 12:16:47 Mass transfer input part [INFO] Order status ==> Success
04/21/2022 12:16:47 Mass transfer input part [INFO] Change status of order on DB
04/21/2022 12:16:47 Mass transfer input part [INFO] End of processing of the following order: ID = 3457
ROBOT 2 :
04/21/2022 12:06:58 Mass transfer input part [INFO] Start processing the following Order: ID = 3457
04/21/2022 12:07:00 Mass transfer input part [INFO] Number of transfers found and accepted by ocr for this order = 27
04/21/2022 12:07:00 Mass transfer input part [INFO] Number of transfers found and rejected by ocr for this order = 0
04/21/2022 12:11:24 Mass transfer input part [INFO] Order status ==> Success
04/21/2022 12:11:25 Mass transfer input part [INFO] Change status of order on DB
04/21/2022 12:11:25 Mass transfer input part [INFO] End of processing of the following order: ID = 3457
PS: The order is exising just once on the database
From your screenshot it is evident that first the Robot03 dispatched the item. Later the item was picked up by your performer/Robot01, which first set it to in progress, completed the transaction and set status to Successful.
Take this example:
If we for some reason had a retry and you have both robots actively working the queue. The retry item is then defaulted to a new item and both robots try to lock it into in-progress but only one of them can takeover the item. This is the round robin algorithm in the working. Read here for an quick overview.
So the thing you observe here is totally normal and as it should be.
In that case are your sure that your queue is entirely without any duplicates? If the dispatcher for some reason has sent the same item two times to the queue, it is possible that both of your robots had to process the same Order ID.
there is no duplicates on the database, also in queues … whats made the both robots take the same line
Execution of first robot :
04/21/2022 12:06:58 Mass transfer input part [INFO] Start processing the following Order: ID = 3457 04/21/2022 12:07:00 Mass transfer input part [INFO] Number of transfers found and accepted by ocr for this order = 27 04/21/2022 12:07:00 Mass transfer input part [INFO] Number of transfers found and rejected by ocr for this order = 0 04/21/2022 12:11:24 Mass transfer input part [INFO] Order status ==> Success 04/21/2022 12:11:25 Mass transfer input part [INFO] Change status of order on DB 04/21/2022 12:11:25 Mass transfer input part [INFO] End of processing of the following order: ID = 3457
04/21/2022 12:12:14 Mass transfer input part [INFO] Start process 04/21/2022 12:12:14 Mass transfer input part [INFO] Closing old application instances
04/21/2022 12:12:14 Mass transfer input part [INFO] Start opening applications
04/21/2022 12:12:14 PM Mass transfer input part [INFO] Recovery of GRC login credentials
04/21/2022 12:12:17 Mass transfer input part [INFO] End of application opening
04/21/2022 12:12:18 Mass transfer input part [INFO] Init draft value = False 04/21/2022 12:12:18 Mass transfer input part [INFO] Start processing next order: ID = 3457 04/21/2022 12:12:20 Mass transfer input part [INFO] Number of transfers found and accepted by ocr for this order = 27
04/21/2022 12:12:20 Mass transfer input part [INFO] Number of transfers found and rejected by ocr for this order = 0 04/21/2022 12:16:47 Mass transfer input part [INFO] Order status ==> Success 04/21/2022 12:16:47 Mass transfer input part [INFO] Change status of order on DB
04/21/2022 12:16:47 Mass transfer input part [INFO] End of processing of the following order: ID = 3457