Hello,

When you throw, in the server action, the "Not CFO" exception, it will be immediately handled in the AllException within that server action. In the client action no exception will be caught since it was taken care inside the server action.

Have in mind that "Not CFO" is a "User Exception" so you can never catch it outside this module since User exceptions are not shareable.

The "Not Registered" handler you have in that client action will only be caught if you throw them explicitely. "Not Registered" means that you don't have a login. This can be managed in the Common Flow instead of a client action since you have to be registered to even reach that code.

Hi @Amritha venkitachalam 

I'd be happy to help you understand the difference between the 'NotRegistered' handler and the 'AllException' handler in OutSystems. OutSystems is a low-code development platform that uses visual development to create web and mobile applications. In this context, exceptions and handlers are used to manage errors and unexpected situations in your applications.

'NotRegistered' Handler:

1. This handler is specific to a particular exception or error that you've identified in your application.
2. It is used when you want to handle a specific type of exception in a distinct way. You configure this handler to deal with a particular error scenario that you expect to happen.
3. In your diagram, when the 'NotRegistered' handler is executing, it means that a particular expected error, which matches the criteria of this handler, has occurred in your application.
4. You would use this type of handler when you know the exact error you want to address and want to define a specific response for it.

'AllException' Handler:

1. This handler is more general and acts as a catch-all for any unhandled exceptions or errors in your application that don't match a specific 'NotRegistered' handler.
2. When the 'AllException' handler is executing, it means that an error occurred for which there is no specific handler defined in your application. This handler can catch and deal with any unhandled exceptions.
3. You would use this type of handler when you want to provide a common or generic error handling strategy for any unexpected errors that may occur.

To summarize, the key difference is in the specificity of the handlers:

1. 'NotRegistered' handler is used for specific, expected exceptions.
2. 'AllException' handler is used for general, unexpected exceptions that don't match any specific handlers.

Hope this will help you!!

Kind regards

Sourabh Sharma

Hi @Amritha venkitachalam ,

Do these images you share come out of some course you are following ??

At first glance, the first one (with image #10) is just blatantly wrong  It is not because at a higher level there is something more specific that the lower action will defer handling.

Closeness of the handler to the exception being thrown trumps specificity.

The explanation with #12 image seems entirely correct.

Discuss this with the person who wrote these pages, as he/she might want to revise the text.

Dorine

Hi @Amritha venkitachalam hope you're well

Judging specifically the two images you provided, seens to me that what's happening is:

1. The diagrams on both images have no differences at all. They are both the same
2. The explanation on the image containing figure #10 is wrong
3. The explanation on the image containing figure #12 is correct. That's what'll happens if you throw the NotRegistered exception. It'll be handled on the CheckCFO flow, since it has a handler (the AllExceptions handler) that could do it. 
   It doens't matter if it's generic, as long as it's on the same branch or hierarchy as the exception thrown.

I think that's similar to what @Dorine Boudry is saying also.

Hope i could help a bit.

Best regards!