[Armin Winkler Has successfully completed the online course IntroductionHas successfully completed the online course Intermediate (200)Has successfully completed the online course Advanced (300)Has successfully completed the online course Basics (100)]

4 months ago #44958

Up

0

Down

::

Hi Leonid,

 

in addition to the potential case of the user’s session token having expired that Daniel mentioned, it could have also been the problem that the user’s device didn’t have an online connection to the Simplifier server in the second they tried to execute the BO in question. Since you are catching the error emitted from the business object by connecting with the error port of the Process Designer activity shape, your customized error dialog was displayed. Hence, it makes it difficult to differentiate the underlying technical error that most likely occured to the user. However, if the BO execution isn’t logged in the monitoring function of Simplifier, it’s safe to assume that the BO script itself wasn’t even executed to begin with, and that could only be if the execution was either tried with an invalid authentication or the server could not be reached altogether.

 

Unfortunately, in both variants you would not be able to see any information in the monitoring of Simplifier, therefore you’d need to create your own error-handling routine for such types of errors.

 

Hope this helps for your understanding.

 

Kind regards,

 

Armin