Logging recoverable errors

This scenario demonstrates how nJAMS can overrule error events with an explicit success event. Assume you have a process that calls an external service. In case the external service is unavailable, your process enters a retry loop to call the external service again after a period of time. If calling the external service fails for the third time, the process terminates in error state. Considering this scenario you would send an nJAMS log error event, if calling the external service fails. If the call finally succeeds, you would subsequently send an nJAMS log success event. In the nJAMS world the entire process execution is evaluated as Success with Error. Otherwise, if the call definitely fails, the entire process execution remains evaluated in state Error.

The following process design reflects this scenario:

nJAMS UI indicates the “recoverable error scenario” as follows:

You can see two error events at the beginning of the process execution, which indicates two failing calls against the external service. The last event is a success event, indicating the process finally succeeds. Thus nJAMS offers a benefit by indicating a successful state containing erroneous intermediate steps.