HI
I’m running Stuido 2025.0.166 STS and trying to use Try/Catch activity but it’s giving me option to check the “ContinureOnError” option. Have a look on the picture.
can someone tell what is wrong and how can i solv this issue?
There is no Continue on error property available for Try Catch activity. By default any error occurs in Try block gets handled in catch block and execution flow continues without any error being thrown.
May I ask why you are looking for that property?
There is no propertied for this action, if any errors occured it will go to the catch section if you find any error in try it will go to the catch block and there you can add your logics in catch body section for more idea on Try catch try to look on below thread.
Hello @Shazi_Latif
If your goal is for the process to continue disregarding an error/exception happening in the Try block, then you would simply keep the Catch block empty.
The process will not stop, as the Exception has already been caught (and ignored).
Regards
Soren
1 Like
Mine is not going to CATCH.. i did write a write text in log message before it goes to TRY and before it goes to CAtch and I can follow in log its not going to Catch area.
I think you enabled continue on error in your try black activity. Make sure you uncheck from each activity and try. It should go to catch in case of exception in the try block.
I tried with both.
First I didt had ContinueOnError on it didt went to Catch.
Then i tried with ContinueOnError on and it didt went.
My exception is System.exception
So i dont know where is the issue.
Can you show your sample flow
Please share your sample project here.
Why would you have Continue on Error for Try/Catch? It would defeat the purpose of Try/Catch.
Hi @Shazi_Latif
Can you please show what all activities you have inside your try block?
And is continue on error enabled for any of those activities inside try?
Also, put a log message inside catch block, so you would know if reached there or not.
Hi all
It does not metter which activity i try with it’s not going to catch area.
I have - 1 Production envoirenment with windows 11 And 1 Production envoirenment with windows 10 and when i try to change download settings for Edge the selector i different..
So im trying to solv with try catch but its not going to Catch area still.
OK I did something which I shouldt do in try/catch as you all said it should go by it self to catch which it’s not doing..
After being tired I tried this.. I added a Throw activity to send it to catch area.. and now its going to catch area.
In that case it was always working as expected.
Its simply that the code in your Try didnt have an error, and as such it never needed to go to the Catch.
The Check App State doesn’t decide if an element not existing is an error, as that might be the desired state. It is up to you to determine that path is an error in your flow and throw an exception as you have done here.
Yes but my issue is here.. that it’s a library workflow and we are not adding any throw in libraries. So that way i wanted to avoid.
Log messages are not considered in a try catch, they are just for logging and will never interrupt your code.
So it is correct and the intended behaviour that it will NOT go to the catch area if you simply log the error via a log message.
You have to throw an exception yourself or the underlying activity needs to throw the exception.
Then you can’t do it this way. Thats a very strange / arbitrary rule.
I am not sure why someone would enforce such a thing. They are extremely valuable in libraries to give clear errors.
First it’s not good prectice and recond if throw comes from library you need to stop process and start again. you can not cotinue the process and it faild the whole process.
What is this ‘good practice’ based from? Cause this makes zero sense to me and is bad practice.
I am not aware of any coding standards that could or should enforce such a rule.
Explain why its bad as a general rule? Perhaps you are creating bad practice in your library activities by not scoping them well.