Hi,

we are using the exception handling tab on our processes to send out an e-mail when a process fails.

we eventually have a retry operator in our exception handling to retry the failed operator a few times.

We'd like to understand how to get access to the actual error that was causing the process to fail. The "Reason" field visible in the dataset of the failed operator seems to contain the most interesting information, however, we do not know how to access it.

We can access all info from the global dataset, but much more than the error_type and some basic information there is nothing to go by.

So how do we get the actual reason for an operator that failed in a nice email to send to the sysadmin?

Thanks!

Does anyone have any help for Maarten?

PAM error handling email with proper error message

This question is Not Answered.(Mark as assumed answered)

MAARTEN DE RIDDER Feb 6, 2015 12:43 PM

Hi,

we are using the exception handling tab on our processes to send out an e-mail when a process fails.

we eventually have a retry operator in our exception handling to retry the failed operator a few times.

We'd like to understand how to get access to the actual error that was causing the process to fail. The "Reason" field visible in the dataset of the failed operator seems to contain the most interesting information, however, we do not know how to access it.

We can access all info from the global dataset, but much more than the error_type and some basic information there is nothing to go by.

So how do we get the actual reason for an operator that failed in a nice email to send to the sysadmin?

Thanks!

You can access by using the Source parameter of the Exception Operator. For example, if the Exception operator that activates is called "UnidentifiedException", then you can get the reason by using 'Process[Process.UnidentifiedException.Source].reason'.

Here is an example where the process tries to run a program, but fails because no information was provided in the operator. The Exception operator actives and then the JavaScript operator extracts the reason from the exception source and stores it in a process level parameter called "errreason".

Thank you so much Benjamin, we will sure give this a try!