You are here:
Configure Automation Failure Handling
Define how Dynamic Revenue Orchestrator (DRO) handles an auto task or callout failure with fallout rules and fulfillment step retries.

Use more general search terms.
Select fewer filters to broaden your search.
You are here:
Define how Dynamic Revenue Orchestrator (DRO) handles an auto task or callout failure with fallout rules and fulfillment step retries.
| Available in: Enterprise, Unlimited, and Developer Editions |
Determine what DRO does when automated steps fail. For example, set up a rule so that a callout responds to error code 402 by retrying up to three times. Then if the callout still fails, it gets assigned to a specific queue for resolution.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.