Apply JMS retry pattern
The complex integration process is divided into smaller integration flows to enable more manageable retries, reducing the risk of partially processed messages and unnecessary retries. Errors are caught in an exception subprocess, logged in the designated logging system, and the process returns an errored state. Any errored flows will automatically trigger a JMS retry through the SAP Integration Suite. The JMS retry pattern can be configured within the JMS consumer process. JMS messages that are not successfully processed and are pending retry can be found in the JMS queue. If the error is due to logic or data issues, the root cause must be resolved first; otherwise, retries will not function as expected.
JMS publisher and consumer processes are introduced before making Pricefx API or OData API calls, meaning that if the Pricefx API fails, only the Pricefx part will be retried. This error-handling approach is optional and can be excluded by configuring the outgoing process to bypass the publisher process and go directly to the next step.
Reference: