What is an exception subprocess in SAP CPI?
An exception subprocess in SAP CPI is a special subprocess inside an integration flow that runs automatically when a step throws an error. It captures the error context, can classify the failure, and ends with an Error End, Escalation End or End Message event, which decides whether the message shows as failed, escalated or completed.
Without one, an error ends the flow abruptly with a technical message and no control over what the sender receives or who is notified. With one, the flow decides.
Inside the subprocess, the error text is available through the exception.message expression and the full exception object through the CamelExceptionCaught exchange property. For HTTP receiver failures, a short Groovy script can read the status code and response body from that object, so a router can send transient errors one way and business errors another.
| End event | Resulting status | Use when |
|---|---|---|
| Error End | Failed | The message could not be processed and must be retried or investigated |
| Escalation End | Escalated | A defined business exception needs attention |
| End Message | Completed | You deliberately returned a controlled error response to a caller |
Never use End Message to hide a failure: the monitor turns green while data is lost. Build one reusable pattern and apply it to every flow. Follow the step-by-step exception subprocess guide.
Related questions
See what Spanovix would fix in your landscape
Bring your hardest interfaces. In a short working session we show where the agents cut failures, manual work and risk for your teams.