Hello Community,
Get Next Item - an Action from the Work Queues native Blue Prism object always worked in a predicted way - usually without constraints, sometimes there was a timeout and then it crashed but the outcome was the same as the actual result.
However, last time we encounter a very strange issue that the output (Item ID) is empty even though the item is being locked by the process. As a final consequence, the bot assumes that nothing is locked, goes to the last steps of its workflow and when it finishes smoothly, Blue Prism issues the status of Automatically set exception on session end for the queue item.
Do you know what might be the reason? Can infrastructure / low performance have any influence on this weird behavior?
Thank you in advance,
Paweł
