An integration developer is configuring an integration flow that must process messages from an SAP S/4HANA system via the SOAP adapter and then write them to an SFTP server. The developer needs the integration flow to retry the SFTP write up to three times if the SFTP server is temporarily unavailable, and to route the message to an Exception Subprocess only after all retries fail. Which configuration achieves this?
SAP Cloud Integration does not offer a built-in retry counter on the SFTP adapter, so the reliable pattern is to place the SFTP call in a Local Integration Process and implement retry logic with a looping or scripted counter. After the configured number of failures, raising an exception routes control to the Exception Subprocess.
Why this answer
Because the SFTP receiver adapter lacks a configurable retry counter that escalates to an Exception Subprocess, the developer must implement retry logic in the flow. Placing the SFTP call in a Local Integration Process and looping with a counter, then throwing an exception after three failures, gives precise control and routes to the Exception Subprocess as required.
Exam trap
The trap here is expecting a receiver adapter to provide a built-in retry counter that escalates to an Exception Subprocess, when that logic must be built in the flow.