Documentation states:

"When no code attribute exists and no match to a defined attribute exists for an onFault element at a level, Sterling B2B Integrator moves to a general onFault (no code attribute) element. If Sterling B2B Integrator does not find a fault code, Sterling B2B Integrator halts the process."

https://www.ibm.com/docs/en/b2b-integrator/6.0.3?topic=oe-when-fault-code-does-not-match-onfault-code

However the last sentence in this is not what currently happens.

in a BP sequence where one or more onFaults (code="xyz") are defined for specific exceptions but there is no General onFault (no code) to handle other unanticipated exceptions, the Error will be logged for the workflow step, but then the engine will not Halt as it is supposed to do, but rather continue processing steps after following the sequence. An Decision with the Advanced Status of -1 is logged in this instance.

Without a background monitoring tool (such as Control Center) with rules to capture errors from these BP(s), there is no visibility that the above error took place and the exceptions can pass unnoticed.

Allowing a process to continue after an unmanaged exception could cause even bigger complications further down the workflow path where output from the activities in the sequence that contained the exception are expected.

Example

Sequence main

Sequence Try This

Activity - A

Activity - B

Activity - C

OnFault code = AnticipatedError1

Sequence Handle AnticipatedError1

OnFault code = AnticipatedError2

Sequence Handle AnticipatedError2

End Sequence - Try This

Activity -D

Activity - E

Activity - F

End Sequence Main

Now say Activity B throws an system exception which we will call "Unanticipated Error"

Activity B will have Error Status

Decision Service "-1"

BP Continues at Activity D....

BP ends state Completed with Error

Expected behavior for an unmanaged/unanticipated error is to Halt at Activity B so that the system operators can see and decide how to handle the exception.