What behavior does the Escalation End Event trigger in an integration flow?

In SAP Cloud Integration, the Escalation End Event is used in subprocesses. Let’s analyze its behavior:

Step 1: Event Purpose- It signals an escalation (e.g., a timeout or condition) from a subprocess to the parent process without halting execution.

Step 2: Evaluate Options-

A. Error without interrupting: Errors use Error End Events, not Escalation.

B. Error and interrupts: Incorrect; escalation isn’t an error—it’s a controlled signal.

C. Notification without interrupting: Correct; it notifies the parent (e.g., via an Escalation Start Event) while the main flow continues.

D. Notification and interrupts: Incorrect; it doesn’t stop the main process.

Step 3: Behavior- In a subprocess, an Escalation End Event triggers a corresponding Escalation Start Event in the parent, acting as a non-disruptive notification.

Step 4: Official Verification- The SAP Help Portal’s "Defining Escalation Events" states that it "signals an escalation to the enclosing process without terminating the main flow."

Conclusion: Option C is 100% verified per SAP documentation.References:

SAP Help Portal: "Defining Escalation Events" (SAP Cloud Integration)

SAP Cloud Integration Documentation: "Process Events"