The Activites package isnt working as expected . What could be the reason ! Is there any new version upgrade ?
Tag queue items with batch ID (filename_timestamp). When performers finish a batch, last bot auto-triggers reporter.
-
Dispatcher runs continuously - Watch input folderNew file → read records → AddQueueItem with Reference = “File1_20251129_0100” Move file to Processed folder
-
Performer (REFramework + Queue Trigger) -
Orchestrator: Queue trigger, Min Items=1, Max Jobs=5
In Process.xaml (after SetTransactionStatus) -
- Get Queue Items (filter: Reference=transactionItem.Reference, Status=New or InProgress)
- If count=0 → all done! Start Job (Reporter process, pass batchID=transactionItem.Reference)
- Reporter Process -
Arg: batchID
Get Queue Items (filter by batchID) → build Excel with statuses → email/save
That’s it! Test with 2 files first.
Aa per my understanding it’s not possible without some process logic.
Stick with performer check - it’s the standard, reliable way.
Use the Dispatcher–Performer–Reporter model with Queue Batch IDs. This is the simplest and most stable way for 24/7 processing when multiple input files can come at any time.
The Dispatcher keeps watching the input folder continuously.
When a new file arrives ,Read the file ,Create a BatchID like FileName_20251129_1530, Then Add every row to the queue with Reference = BatchID, Specific Content = row data.
Then move the input file to “Processed”
In this BatchID easily group all items belonging to one file.
You run 5 performer bots in parallel using Queue Triggers.
Each performer will do only one thing ,takes the item, Processes it and Updates its status (Success/Business Rule Exception/System Exception)
Inside the Performer, after completing a transaction:
Use activity Get Queue Items with filters:
Reference = BatchID and Status = New + InProgress
If the count = 0, it means this batch is fully processed (like all 100 items from that file are done)
Now (only once), start the Reporter job. Reporter shall receiveBatchID as an argument.
Here * Use Get Queue Items (filter by that BatchID), Then Build Excel summary report, you can email it to SME or store in a folder
This report contains only the items for that specific input file.
If this design helped you fix the problem, please mark as solution so it can help others too.
atch Folder + Per-File Batch Processing Just run one 24/7 process that monitors a folder and processes each input file as its own batch.
How it works:
- Bot runs continuously and watches an Input folder.
- When a new file arrives, the bot picks it up.
- It reads the file and processes all records inside that file only.
- As soon as it finishes that file, it generates a report for that file.
- Move the file to Processed and return to watching for the next one.
I find people over complicate these solutions, messing around with timestamps etc, because they aren’t aware of some of the great features that have been in UiPath for a long time.
In your Dispatcher, if you add the UiPath.Persistence.Activities package you will get some new activities that allow you to have your process wait for other things to complete before it resumes. In this case it can wait on the queue items.
If you use those persistence activities to add the queue items, and then wait for each of them in a loop, you’ll end up with a workflow that will resume once all the queue items are done, whats even better, it will have the details of the items it created, and their updated statuses / data, so you can do your reporting there directly, without messing around trying to read the queue items that were completed in this period.
Relying on timestamps simply doesn’t work well if you have retries and lots of parallel processing, but my suggestion does.
you are right we dont require dispatcher and performer bot