I have automations which complete work in batches rather than at individual transaction level. Ie the robot may go and download a report of 1000 transactions before executing the 1000 transactions on a system. On Insight it looks like the dashboard is seeing this as 1 run or job which means on the ROI dashboard we struggle to get the values accurate as we should be accounting for the fact this saves our customers 1000 transactions of work to complete. Any help on how to overcome and have the ROI at that transaction level ? ie ROI is 1000 transactions multiplied by a 5 minute save rather than 5 minutes multiplied by 1
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Watch the videos on our official YouTube channel for more visual tutorials.
Meet us and our users on our Community Slack and ask your question there.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
Cheers from your friendly
hey @gary.wright, so Insights only gets the last log event and error logs, so the only way for you to record the number of “batches” (which for us at UiPath are actually considered a transaction), you would have needed to log the number of transactions at the end of the workflow. However, best practice for this kind of situation is to use a queue, since we have the ability to track the number of queue items without any extra work on your part.