Unexpected Behavior with Retries in Queue when Unique Reference Enforced

Help Orchestrator
,
1

Hello everyone,

I have a question related to the unique reference property of a Queue, and I believe there might be a bug or something I’m missing. Please take a look at the scenario described below:

The process is developed using the REFramework with the Dispatcher and Performer concept.

Lets Say-

  1. I have created a Queue with Auto Retry set to 1 and Unique Reference enforced.
  2. I executed the dispatcher and added a few queue items, let’s say 10.
  3. Upon running the performer, it fetched a new queue item for processing. However, the processing failed on the first attempt. Since a retry is configured, a new Queue Item with the same ID (as per the REFramework Template) was added to the queue with a “New” status.
  4. Before proceeding to process “Transaction 2” or any other new queue items, I stopped the process.
  5. During the end state of performer, let’s assume that I deleted all queue items with statuses other than “New” (as required by the process).
  6. I initiated the dispatcher once again.
  7. Now, I attempted to add the same queue item that was added in the previous run of the dispatcher. (This is the queue item that initially failed and was added as new due to the retry rule of the Queue.)
  8. Strangely, the queue item was added again, resulting in two “New” queue items with exactly the same reference. This is surprising considering the unique reference enforced.

So, my question is: Since there is already an existing “New” queue item with the same reference, how is it possible for a new queue item with the same reference to be added? Doesn’t this situation contradict the entire rule of enforcing a unique reference?

Best regards,
Devasya Singh

2

Can you double-check that the “Enforce unique references” is enabled? And upload screenshots of the setting, and of the queue transactions with the 2 transactions that have the same reference?

image
image692×341 28.8 KB

3

@efelantti Sorry for the delay. As per security policy I can’t share the actual data. Although, I am attaching a sample example scenerio.

Queue Setting
Queue Setting1090×525 27.3 KB

No of items with Ref
No of items with Ref1106×529 39.6 KB

Main flow
Main flow690×806 28.7 KB

Bug in Queue when Unique Reference Enforced
4

Could someone please create a scenario based on the snapshot and provide a response?

5

Thanks for the sample, I tested it and was able to recreate the scenario on UiPath Studio CE 2023.8.0 and Cloud Orchestrator.

I tested it as well on Studio 2022.10.7 and Orchestrator 2022.10.3 - but there it wouldn’t be possible to add the 2nd item with duplicate reference. So, it seems to be a bug with the new version(s). Good catch, @devasyasingh!

Could you check this @loginerror?

6

@efelantti , Thank you for your effort. It appears to be a bug. I have created this scenario in Studio version 2020.10.7 and Orchestrator version 2020.10.7. Therefore, I suspect that this issue might exist across different versions.

@Raluca_Laic @loginerror @David_Barzi any thoughts?

7

Now that you mentioned the version your using, I went back and tested again on 2022.10 and found a small mistake on my part in creating the scenario. Turns out the issue is on that version as well.

8

Replying to keep the topic fresh and visible.

9

Hello everyone,

There hasn’t been any clear clarification provided by any of the forum members or UiPath representatives. Therefore, assuming the issue is a bug, I am marking this comment as the solution to close the matter.

I have also reposted this issue in the Bug section of the forum. You can follow the updates here:

Thank you for your attention.

Happy Automation!!

10

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.