Hello please, I am new using Uipath, I am finishing the Academy but have one doubt regarding the utilization of log activities and scratches for identify errors.
I would like to know the best practices.
The tool has as default the logs enabled.
Should I to implement in specific activities on my process Log Messages, Scratches or only during the DEV?
Should important too in production I have one better control and configure logs on the important activities as for send me one email alerting problems ?
At this time I won’t to use Orquestrator and I don’t kwow if the tools has the option for advise us when one job stopped.
Thanks
Welcome to UiPath Forum!
The ‘Log Message’ activity will definitely help you during Development as well once the process into Production. After looking into the orchestrators log you can identify how the business flow is running and of course same will help you to troubleshooting any unexpected error occurred during the run.
Best Practice:
Step 1: Keep an excel sheet to store exception code and description as in the inline screenshot. Where EXSYS → indicating System Exception Message and EXBRE → indicating Business Exception Message.
Step 2: Read the error code and description from the excel and load into a ‘Dictionary’
Step 3: Make use of that Dictionary through out your process by calling the Dictionary as in the below inline screenshot.
Hope this will help you. Thank you.
Hello!
Thanks, I am a little confuse how I could organize the logs using Excel and dictionary.
Do you have one example for my understanding?
Please
We need to keep error logs (System & Business exceptions) alone in the excel format and then using a dictionary to read the value as in my previous post. If you need an sample code for that, please let me know.
For normal log/trace messages, you can write those in following example cases,
- While launching an application to check successful log
- While extracting some key values from any application.
- While checking some conditions or sending out any notification email to specific recipients.
- After completing any main or sub functionality of the process. Ex: Policy creation, Payment, Policy Validation etc in an insurance process)
- During any unexpected error, log the message before throw activity.
Note: Don’t capture any sensitive information to orchestrator log. In very exceptional cases you can do this.
Thank you.
Hello , thanks by feedback.
Could only please given one simple example to clarify, for generate the log for two activities?
1- Failed to Read Range of Excel file (critical error)
2- Sucess to Append line in txt file (Info).
Hello, if you can will help me with only two examples of generate logs.
1- Failed to Read Range of Excel file (critical error)
2- Sucess to Append line in txt file (Info).
Thanks a lot.
Hello, please could you help with one example in xaml? Could be the logs for write the problem to open excel app or openning the browser.
Thanks
Default log message will store it In text file automatically. If you want to store the error message the use append range or write cell activity
Regards,
Arivu
Hello,
Ok, I am trying to configure Catch for the option Read Excel Range with Excel App Scope but is not little working.
The catch is not working with READ RANGE neither with for the process of Openning the Browser. Could you guide me how I include the catch for check error of excel open and not getting to open the browser? I am sending in attached how is configured the app scope.
Doc4.docx (243.4 KB)
I configured with send message of Outlook and it works.
The activity Read range I got to configure the log but How can I finish all process(activity)?
The workflow is going on after Log message.