Create a retry policy to automatically retry failed requests when a step encounters an intermittent issue.

1. Navigate to IntegrationHub > Retry Policy > Create New.
2. On the form, fill in the fields.

   Table 1. Retry Policy form

   Field	Description
   Name	Name to uniquely identify the retry policy.
   Connection Type	HTTP
   Condition	Conditions that must be met to trigger the retry policy. Conditions that trigger a retry policy include the is, is not, contains, and contains not operators.
   Retry Strategy	Exponential Backoff: Option to exponentially increase the time interval for the subsequent retry attempts. The multiplier is 2. Fixed Interval: Option to specify a fixed time interval after which a retry attempt should be made.
   Interval (seconds)	Time interval in seconds after which a retry attempt should be made. Note: If Retry Strategy is Exponential Backoff, the time interval exponentially increases after every retry attempt till the maximum numbers of attempts is reached.
   Count	Maximum number of retry attempts. If no value is specified, the maximum number of retry attempts is based on the value provided in the glide.fdih.retry.max_count system property. Default value of the glide.fdih.retry.max_count system property is 0. For more information about system properties, see Available system properties.

3. Click Submit.

Example: Retry policy with Retry Strategy as Exponential Backoff

In this example, the policy is defined to attempt retry when one of these conditions is met:

• HTTP Method is GET and Error is Connection Timeout
• HTTP Method is GET and Status Code is 429

When the condition is met, retry attempts are made for a maximum number of three times. The time interval between the retry attempts is exponentially increased. The time intervals in this example are 10 seconds, 20 seconds, and 40 seconds.