Display Logs in Each transaction Item info of Queue

Each Transaction Item in the Queue should display all Logs of that particular Transaction
so that it wont be a time taking process to search for that particular transaction from Bulk of logs at Robot level or Job level Logs

2 Likes

Hi @vinay_reddy,
Can you say a little bit more. At the moment I thing than putting all logs about transaction to particular Item can make it less readable and provide a lot of unnecessary logs when it comes to analyze all data etc.

Hi Pablito ,
Let’s say below process is put for a schedule to run every hour
And each job processes around 200 Records / Transactions

When bot process those transactions , at the end of the day if i want to look for a particular transaction , why it got failed or want to check the logs for that transaction the current situation is either i can view the Logs at Robot level or can view logs at Job level

which is very difficult to track in between wholesome of the Logs , what my idea here is
Logs of that particular transaction should be shown at that particular Transaction details only

@vinay_reddy,
Thank you for your suggestion. I added it to our internal ideas tracker for our team to consider.

2 Likes

Not using Orchestrator at this moment but this looks handy feature therefore +1

2 Likes

Up!
That still is a really awesome feature to add on this year version

I assume nothing happened regarding this? I just moved from BluePrism to UiPath and I miss this feature very much.

Hi,
I’ve checked our backlog. From the information I have, it looks that this feature is planned for one of the future releases but we don’t have any exact date that I could confirm.

1 Like

Cannot wait for this feature to be added!
This would make debugging a lot, lot easier!
:heart:

1 Like

Any news on this feature?
Viewing the logs of 1 specific transaction directly from the transactions view would make life a lot easier.

I continue to support this new feature. But, for now, what you can do is to use the “Add log field” activity, pass the Transction Reference, and use this to filter a single transaction from all the logs. I dont think that the Orchestrator enable this kind of filter, but you can export the logs and check using another tool made exclusive to handle large number of logs rows/files.