Set Up Retry Policies for Failed Callouts

You can create policies that control how Order Management retries failed callouts to fulfillment systems. You can design callout so that if it fails to connect to an external system, it retries that connection based on the policy that you set up.

Note

For retry policies to work, your org must be running in PlatformEvents mode. See OM Standard: Platform Events for Orchestration

Follow the steps on this page, or follow a link on each step to find more detailed instructions.

If you don't want to set up a policy, but instead want only to add a retry rule to a single orchestration item, see Add a Number of Retries to an Orchestration Item Definition

1. If you're running a CME version before the Spring '22 release, follow this step. Otherwise, you can skip it: Add the integration retry policies to the custom record type settings. See: Enable Retry Policies in the Custom Record Type Settings
2. Set up a retry policy from the Integration Retries Policy window. See Configure an Integration Retry Policy
3. If you have set up a retry policy, then associate that policy to an orchestration item definition. See: Associate a Retry Policy with an Orchestration Item Definition
4. OM Standard only: Click Start next to Schedule Integration Retry Job in the XOM Administration Panel. See Schedule the Integration Retry Job in Order Management Standard
   

   Note

   OM Plus only: You can also define a default timeout and retry policy that applies to all auto tasks and callouts that aren't explicitly specified to follow a different policy. See System-Wide Timeouts and Retry Policies in OM Plus