As I understand the queue items in the Orchestrator Cloud are only retained for 180 days and then deleted (or archived if using a blob storage). As I would like to keep the data on the queue items for dashboards, reporting, etc. my thought is to “backup” the queue item details to a separate SQL database.
I can retrieve the details using the UiPath Web API. However I am not sure about the uniqueness of the IDs when having multiple tenants. Can the ID of a queue item in one tenant potentially also be used in another tenant? I also found some documentation stating that the folder ID might change e.g. if changing to another license type.
In the swagger documentation for QueueItems I can see that OrganizationUnitId is deprecated. From what I can see this is the link to the folder the queue item exists in. How can I then know where the queue item/queue resides in?
Additionally, I cannot seem to find a solution on how to link the process name of the process that processed the queue item.
Any thoughts on this? Maybe a design suggestion if you already have experience with this.
Yes - it is still working and hence I also included the value in the initial design of the database that I am working on. But while I was trying to find documentation on uniqueness of ID’s in general I came across the OrganizationUnitId being deprecated.
However I read somewhere else that while the ID of a folder might change due to change in license the key of the folder never changes. It could be that the folder key is going to be implemented at some point in time instead of the ID.
Could be. It might be worth contacting UiPath directly about it, I’m curious what they recommend.
And the other options? You already noted archiving to an UiPath or external storage bucket? You can use the CSV’s from there to load your SQL. Might be easier at this point in time.
Another option would be to use UiPath Insights, it’s the build in tool for dashboarding & reporting up to 5 years.
Anil_G
A_Learner
Matias_Clemente.Arg