It seems that the queues used in the Orchestrator are designed to be used once.
I find myself in the situation where it correctly processes all the items in a queue but I can’t find a way to return the status of ALL items in the queue to “new”.
My idea is to use that queue once a month, since it will contain the same items, but I should put them back to the state equal to “new”
Also, I’m thinking, if I can’t reuse that Queue, should I empty it before using it again? Or do I just reload the queue with the same elements?
Is there a limit of items for use?
So, could you clarify for me what would be the scenario in which queues are used correctly?
Is there a way to do what I say without having to go through each item in the queue?
For making a queue item to new state only way is to mark it as “Failed”. And then retry the queue item. It will generate new queue item.
To do so you will need to create a sequence that will first get queue items thats are not new items and loop through each queue item, mark it failed by using Set transaction Item Status to failed business exception.
After all queue items are done go to the queue select all queue items and click retry.
Ok, but the philosophy behind queues, were they made to process items only once? and reload them every time I need them? That idea seems strange to me since if they are the same every time it would be like an unnecessary burden
Yes you have to load the items everytime you need…that is even if it is same item to be processed you can add them again
So for example you are running the process for about 6 months and after 6 months if you need a report of all the successful and failed transaction in last 6 months then in case of what you are asking to have change yhe status back to new we wpuld not have the trace of what happened as well…so those items are closed and new items are to be added so you have a complete trace of what happened over time…
And yes you can add any number of items there is no limitation as such…the old items gets archived based on the archival policy you have in your organization…bormally for cloud it is 6 months or 1 year archival