Skip to Content (Press Enter)
Back to Ideas
7
Like
Follow Idea
[Reactive]User Exception Handler does not work
541Views
9Comments
New
Frontend (App Interfaces)

Original story:

Create a new User Exception and throw that exception.

I expect it to be caught by the User Exception Handler, but it gets caught by the All Exceptions Handler.

In the case of Traditional, it works as expected.


After contacting support, I was told that this behavior is by design.

However, this means that it is a flawed part that can place a User Exception Handler but does not catch any errors.

I feel this is a big problem.

05 Mar 2021
Copy link to comment

Hi Yuichi,

First your post is not an idea.

Second, I don't believe it is true what you write, not that the exception is only caught by the All Exception Handler, nor that OutSystems is correct to state that is behavior is by design.

If you add the User Exception handler in the OnException action on the Common flow it will be caught there. If you add the User Exception handler in the action as you showed in your screenshot it will be caught there.

I have tested this behavior, see the breakpoint at the user exception handler flow.

Regards,

Daniel

06 Mar 2021
Copy link to comment

Hello Daniël


As a result of contacting the support site, I was asked to post an idea, so I am posting it here.


Also, what you have verified is a little different from what I posted.

I'm wondering if it doesn't work properly if I put UserExceptionHandler in place. The screenshot you posted is UserException1Handler. I know that this implementation works fine.


I want to implement common exception handling, so I want to use a common UserExceptionHandler instead of a separate UserExceptionHandler.

08 Mar 2021
Copy link to comment

Hi Yuichi,

I see now, indeed the behavior is different whether one uses UserExceptionHandler or UseException1Handler. 

But I still find it strange that OutSystems supports suggest to create a idea about it.

I will as the product team for a response.

Regards,

Daniel

08 Mar 2021
Copy link to comment

According to my contacts at OutSystems this might be a bug, and for that they ask you to please report it via the feedback button in Service Studio, ideally with including the module, or a module that just shows the behavior.

If you report it via the feedback button, then it will directly be visible on the backlog of the product team to prioritize and analyze.

08 Mar 2021
Copy link to comment

Also report on forum few weeks back, also there it is mentioned OutSystems product team considers this a potential bug, not an idea.

https://www.outsystems.com/forums/discussion/68558/how-to-handle-core-widget-exception-in-the-end-user-application-as-user-exception

08 Mar 2021
Copy link to comment

Hi Daniël,

Following your advice, we provided Service Studio feedback. It also lists the escalation number when I contacted support.

Regards,

Yuichi

08 Mar 2021
Copy link to comment
Changed the category to
Frontend
17 Jun 2021
Copy link to comment

This is not an idea, indeed, but rather a bug report. However, I saw your forum thread in which you said that Support suggested that you post this as an Idea.

In any case, this is not the correct error handling behavior. It must behave the same, regardless of application kind (Reactive/Mobile/Trad. Web).

I hope this gets fixed soon.

26 Jun 2021
Copy link to comment

A fix for this issue will be included in Platform Server version 11.13.0.

11 Aug 2021
Copy link to comment

Hi Nordin,

That's good news!

16 Aug 2021
Copy link to comment