I have an issue where I am confused as to the logic of queue items being added in the Orchestrator Queue. I use an “Add Queue” Activity to insert items in the Orchestrator Queue from an application row by row, and I have a unique reference for every single item.
Initially I thought that when I load them into the Orchestrator Queue they are added one after another. First item is added, second item is added above the first, third above the second and above the first etc., and when the robot works each item it works them from the first one added to the last (so from oldest to newest, FIFO).
However by using the reference field I noticed that the Queue Items become rearranged and have different orders. This causes the robot to jump across tickets in the application and not work them sequentially.
Has anyone else encountered this issue before? Is there a way to remove this “sorting” capability for the queue transactions?