Handling unique Reference with queues

Hi,
I built a dispatcher that is crawling a web page for specific data.
In case the dispatcher runs again before the performer has finished running on all of the transactions then the same queue item might be added again.
I thought of adding a unique reference to the transaction, I even surrounded that with try-catch block (because there is an execption if I add the same reference) but then even if I have a transaction with “Removed” status it is still not added to the queue.
Why is that? And would like your suggestion on what is the best way to the handle this issue?

Thanks alot

Tal

@talsha

Can you share few screens regarding the problem

Thanks


image
image
image

hi
I shared the transactions from the queue with the reference. The 1st one is the one which is deleted and I cannot add it again.
I want to be able to add it if the same reference is already deleted.

Thanks

@talsha

Can you filter the queue with the Unique reference(77229Final)?

Provide the screen

Thanks

It is just the one that you see