Hi @Mukesh Kala Time stamp: 20:30 video As you mentioned Number of times retry is configurable, Please guide me HOW DO I configure that one FROM Orch Asset or Excel config file. How do I pass values to this module?
Hi, 1. To Pass from Orchestrator - Make an Asset of Type Integer and store the Count in it. In Studio - Use Get Asset activity - Pass the Asset Name and Get the Value. 2. Since GE Handler is not part of RE Framework , You would need to write Code to use a Config file in Sequence or Flowchart. Below video explains the same. ruclips.net/video/t0NgDWJTfro/видео.html
@@MukeshKala Mukesh i need your suggestion pls last week I did my certification but I got 62 % i didn't pass it ..I already covered my all topics ..do you do advanced level certification training as well ?
Yes , we can have a Message Box in the GE Handler. As we have the errorinfo passed as Input Argument to the Handler , we can use the below expression to get the Exact exception Type. errorInfo.Exception.GetType.ToString Having said that , Just an Advice - if you are doing an Unattended automation , then Message Box would not make sense as it will pause your execution with the Message .... further you can use the orchestrator log / custom logs to store this information.
When the Global Exception Handler encounters an exception, it logs the name of the activity which faulted and starts retrying the activity three times. If it encounters the same exception each time and the number of retries reaches 3, the execution is aborted at the level of the activity which threw the exception This 3 is in the IF block of Choose Next Behavior Read this docs.uipath.com/studio/standalone/2022.10/user-guide/global-exception-handler
Hi Mukesh, Your tutorial is misleading / incorrect regarding the try catch part. You specify that 'Only uncaught exceptions will reach the Exception Handler. If an exception occurs inside a Try Catch activity and is is successfully caught and treated inside the catch block (and not re-thrown), it will not reach the global exception handler.' This is not correct. That only occurs if the faulting activity is at the very top of the try catch, as in your example. But put that same activity within a sequence and the failing activity will hit the try catch, as will every container above it until it reaches the Try Catch. By all programming standards the faulting activity would be considered 'caught' by the try catch and a global exception handler wouldn't fire, but UiPath has developed this as a First Chance Exception handler, making it only really useful in incredibly simple projects or for logging.
@@MukeshKala I understand your confusion. UiPath describes it in the manner you did in your tutorial, but as I'm sure you know, UiPaths documentation isn't always accurate which is why people turn to these sort of resources, so its important they are accurate.
thank you for pointing out. i was also confused at the end when he shows handled exception also appeared in Global handler which was contradictory to the statement he made initially.
I cleared the exam today. Your videos were a great help in understanding concepts. That's why I am commenting first time under a video
Great job! Thank you for sharing
Explained very well and It is Very Helpful video.....👌👌
Cheers Bro , Thank you for the comment 😊
Extraordinary explanation
Glad you liked it
Really Helpful . Many interview questions are also covered .
Thank you ☺️ , Glad it was helpful 😃
Thanks for very crystal clear explanation Mukesh.
As always your videos are easily understandable.
Please keep uploading the new videos.
Thank you, I will
picture perfect...you got good teaching skills bro...! very useful.
Thank you , Appreciate your Feedback 🤓
Thank you so much 🎉❤
You’re welcome 😊
Thank you for the wonderful video. When there are nested activities the global handler is getting invoked multiple times , how to avoid that .
Can you please explain the scenario in bit more detail
It's simple and very helpful for beginners.
Awesome 👍
Thanks a lot 😊
great video!!
Thank you for your feedback 🙂
Hi @Mukesh Kala
Time stamp: 20:30 video
As you mentioned Number of times retry is configurable, Please guide me HOW DO I configure that one FROM Orch Asset or Excel config file.
How do I pass values to this module?
Hi,
1. To Pass from Orchestrator - Make an Asset of Type Integer and store the Count in it. In Studio - Use Get Asset activity - Pass the Asset Name and Get the Value.
2. Since GE Handler is not part of RE Framework , You would need to write Code to use a Config file in Sequence or Flowchart. Below video explains the same.
ruclips.net/video/t0NgDWJTfro/видео.html
Great explanation easy to understand 👌 👍
Thank you For the comment 😊
@@MukeshKala Mukesh i need your suggestion pls last week I did my certification but I got 62 % i didn't pass it ..I already covered my all topics ..do you do advanced level certification training as well ?
Drop me your mobile number on mailmukeshkala@gmail.com and let me give you a call ..
Good stuff " Muka 💯💟"
Thank you Mahesh for the comment and the NickName as well 😉
@@MukeshKala lol my nick name is Mailo too 😀
@@MukeshKala I have 2 cousins and 2 friend name '' Mukesh"...I call them " Muka " with love...
Super 🤩
Nice explanation...i have a doubt can we make message box for what type exception occurs in global exception handler like we can see in catch block ?
Yes , we can have a Message Box in the GE Handler. As we have the errorinfo passed as Input Argument to the Handler , we can use the below expression to get the Exact exception Type.
errorInfo.Exception.GetType.ToString
Having said that , Just an Advice - if you are doing an Unattended automation , then Message Box would not make sense as it will pause your execution with the Message .... further you can use the orchestrator log / custom logs to store this information.
@@MukeshKala thanks
i have a doubt.... plz reply .... where is retry mechanism in the g.e handler .... how it will be increase the counter
When the Global Exception Handler encounters an exception, it logs the name of the activity which faulted and starts retrying the activity three times. If it encounters the same exception each time and the number of retries reaches 3, the execution is aborted at the level of the activity which threw the exception
This 3 is in the IF block of Choose Next Behavior
Read this
docs.uipath.com/studio/standalone/2022.10/user-guide/global-exception-handler
thank u sir
Welcome
Awesome 🙏
Thank you! Cheers!
Hi Mukesh,
Your tutorial is misleading / incorrect regarding the try catch part.
You specify that 'Only uncaught exceptions will reach the Exception Handler. If an exception occurs inside a Try Catch activity and is is successfully caught and treated inside the catch block (and not re-thrown), it will not reach the global exception handler.'
This is not correct. That only occurs if the faulting activity is at the very top of the try catch, as in your example. But put that same activity within a sequence and the failing activity will hit the try catch, as will every container above it until it reaches the Try Catch.
By all programming standards the faulting activity would be considered 'caught' by the try catch and a global exception handler wouldn't fire, but UiPath has developed this as a First Chance Exception handler, making it only really useful in incredibly simple projects or for logging.
Hey Jonathan,
Thank you for that - I would definitely go back and have a look at it.
@@MukeshKala I understand your confusion. UiPath describes it in the manner you did in your tutorial, but as I'm sure you know, UiPaths documentation isn't always accurate which is why people turn to these sort of resources, so its important they are accurate.
I will check and make a new video if required , Thank you for pointing it out 👍
thank you for pointing out. i was also confused at the end when he shows handled exception also appeared in Global handler which was contradictory to the statement he made initially.