Orchestrator in Automation Cloud™ - Data Retention and Archiving for QueueItems

Hello Alexandru,

thank you for your reply.
I found myself a workaround, don’t worry. Take it as a feedback and scenario where I indeed want to ensure uniqueness of a reference but at the same time I want to be able to delete some of the items from the queue and then run the dispatcher again to re-add and re-run those.

I could simply Clone them but they are gone due to the retention.
Creating a new queue is not very systematic solution. It is again a workaround.
Overall I think you guys underestimate how the end users are operating with the Queues.
That brings me to some of my feedback here:

I understand the need of improving the performance of your servers. But I think you have to be more graceful and make the retention time much longer, lets say 2 years. Surely it is not that much data, it is just a text in the end. A queue export of cca 4000 items is about 1,5MB big csv. :floppy_disk: