Connection Retry Rules

You can create rules that control how Order Management retries failed callouts to fulfillment systems.

There are two main types of connection retry rules for a connection failure:

• Simple number of retries: Enter a number of retries on a single callout. The orchestration item immediately retries a failed connection, and repeats this process until it either succeeds, or has tried and failed the set number of times. See Add a Number of Retries to an Orchestration Item Definition

  • Pros: Simple to set up for a single orchestration item.

  • Cons: You have no control over the interval between retries. For example, if an external system is down for a couple of minutes, orchestration items make calls again and again without a significant pause.

• Integration Retry policy: Set up a more complex policy that you associate with many orchestration item definitions. For example, you can set how long orchestration items wait before retrying a failed connection. You can associate this policy with as many orchestration items as you like. See Set Up Retry Policies for Failed Callouts

  • Pros: Complete control over how many times an item retries (including retrying forever), as well as the interval between those retries.

  • Con: Takes several steps to set up and apply to relevant orchestration items.

Note

If you set both kinds of connection retry rules on a single orchestration item, it ignores the simple number of retries. Instead, it follows the policy that is associated with it.

• Add a Number of Retries to an Orchestration Item Definition
  You can set the number of retries that an orchestration item attempts after a failure. This topic explains how to set this number for a single orchestration item definition, rather than creating a policy that can be applied more broadly.
• 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.
• Enable Retry Policies in the Custom Record Type Settings
  You can create rules that control how Order Management retries failed connections to fulfillment systems. Before those rules take effect, you must enable the policies in the Custom Record Type settings.
• Configure an Integration Retry Policy
  You can create a policy to control how orchestration items retry failed callouts to fulfillment systems. This step shows how to configure a policy that you've already enabled in the custom record type settings.
• Associate a Retry Policy with an Orchestration Item Definition
  After creating an integration retry policy, associate that policy with an orchestration item definition (a callout). That callout uses the retry policy to determine how often, and how many times, to retry a failed connection.
• Schedule the Integration Retry Job in Order Management Standard
  Start the Schedule Integration Retry Job from the Vlocity Order Management Admin Panel. After you've scheduled this job, it runs according to its custom settings. This job is relevant to retrying failed callouts, as well as moving a system interface to Online status.
• Custom Settings for Integration Retry and System Interface Online Mode
  Order Management allows you to change the default settings for the job that retries callouts, or takes them online when you set their system interface online. The same job does both things, so changing the setting affects them both.
• System-Wide Timeouts and Retry Policies in OM Plus
  You can define a default timeout and a default retry policy that applies to all auto tasks and callouts that aren't explicitly specified to follow a different policy.