Hi. Wanted to ask about these two activites, one adds the queue items one by one another, all together
One has the in built reference option, the other one I have to create a reference column for the orchestrator to get an unique reference.
So I wanted to ask, isnt bulk inherently better? Or like is there any use case when to use which? Thank you
Looping and executing Add Queue Item over and over isnāt ideal, depending on how many items we are talking about. Adding the Reference column to your datatable and populating it is simple. Bulk Add Queue Item has the added benefit of being able to do āall or nothingā or āitem by itemā. I highly recommend using Bulk Add if youāre adding more than a few items.
No. For one you have to create a data table just to use it, which is annoying, and populating the specific content per item can get messy in my opinion. Unless you are making thousands of items looping over a collection wont take too much longer.
I also think the āresultā also being a data table is kind of crappy.
Bulk for sure has its use, but Iād say its only worth faffing about with the tables when you have a huge number of items.
Yes that exactly was my concern. Makes sense now. Thanks
Gotcha. Thanks. makes sense
Bulk Add Queue Items and Add Queue Item are both used for adding items to queues in UiPath Orchestrator, but they serve different purposes and have distinct behaviors that can make one more suitable than the other in specific use cases
Bulk Add Queue Items:
Adds an entire collection (such as a DataTable) to the Orchestrator queue in one call, greatly improving speed and efficiency for large data sets.
Best for batch processing, where all queue items are ready in advance and performance is critical because it minimizes the number of network/API calls with a single bulk operation
When the queue is set to enforce unique references, the source data must contain a dedicated āReferenceā column, since Bulk Add does not allow specifying the reference directly in the activity itselfāit will automatically use the column you name āReferenceā as the itemās unique identifier
If there are duplicate reference values in your source data and the queue requires unique references, those items will not be added to the
Add Queue Item:
Adds a single item to the queue at a time, enabling you to specify the Reference property directly as an argument within the activity at runtime
Best for situations where you need to generate the reference dynamically (e.g., creating a reference on-the-fly or based on runtime logic) or when you need individual processing, validation, conditional business logic, or per-item error handlin
Both has their own pros and consā¦
As always different situations need different flexibilities
When you have a known set or if you are extracting many items to be added to queue ..then bulk add makes sense as already the data is ready we need to add one column reference if needed else we are good to go..
On the other hand add queue item comes in handy many yimes..where you have a chain of processes running at different times and are inter dependant ..or when there are preprocessing steps that we do before adding to queue and next steps also take timeā¦its ideal we use add queue items instead wanting to complete the first step for all items
So choose as per the need that you see and the design that you make
Cheers
Yesss i totally got you and had to do a similar task regarding that. like if we are just directly adding the data w a reference i can use the add bulk queue, but lets say i have to filter out every row with a condition or as you said a chain or process or preprocessing before adding queue where i check each item, then i would use the add queue item only, makes sense. Thanks again. Cheers