--- schema_version: "1" id: b606c44dee8bfa911cb736e5b5c62416e657212a921e1fab8e95a7a9d92cfe7d title: Fallout Design and Management collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_fallout_design_and_management.md canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_fallout_design_and_management.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 0364efc3264c3d2976e18dafec4053761d96323fb8c50697ca28680596475038 description: Fallout refers to fulfillment steps that have failed. Dynamic Revenue Orchestrator (DRO) can retry failed callouts or auto tasks, send them to a queue, or simply mark them as failed. During fulfillment, operators can mark steps as complete, or retry them. products: - Revenue Cloud release: "264" --- # Fallout Design and Management Fallout refers to fulfillment steps that have failed. Dynamic Revenue Orchestrator (DRO) can retry failed callouts or auto tasks, send them to a queue, or simply mark them as failed. During fulfillment, operators can mark steps as complete, or retry them. ### Required Editions
Available in: Enterprise, Unlimited, and Developer Editions
When designing fulfillment, create rules that determine what DRO does when a step fails. For example, set the number of times the step retries before being assigned to a queue for resolution. During the fulfillment process, retry failed steps, or mark them as complete, either one by one or in bulk. ![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_example.png) Example The fulfillment designer creates a rule so that if a Credit Check callout step receives an error from the credit department, the step retries 3 times. If the step still fails, then it goes to the Credit Team Fallout queue. During fulfillment, the credit department's credit check system is down for a few minutes. After the credit check system is back online, the credit team checks the fallout queue, selects all the failed callouts in the queue, and clicks **Retry**. All the steps retry, and since the system is back online, they're all successful and fulfillment continues. ## Design Time Before fulfillment, designers configure fallout in DRO: - Turn on Fallout settings. See [Turn On Features to Manage Fallout and Service Level Agreements](https://help.salesforce.com/s/articleView?id=ind.dro_turn_on_features_to_manage_fallout_and_service_level_agreements.htm&release=264.0.0&type=5 "Turn on features to manage failed or late fulfillment steps.") - Create Salesforce queues to contain fatally failed steps: For example, you can create a queue for each group in your organization that handles fallout. These queues must include Fulfillment Step as a supported object. See [Create Queues](https://help.salesforce.com/s/articleView?id=service.setting_up_queues.htm&type=5&language=en_US). To add fatally failed steps to an existing queue, you must either be a member of the queue or have the System Administrator permission set. Assigning a fulfillment step to a fallout queue does not trigger email notifications or create Salesforce tasks. - Configure fallout rules: These rules tell DRO how many times a step retries, and when. They also tell DRO which queue to send fatally failed steps. See [Configure Fallout Rules](https://help.salesforce.com/s/articleView?id=ind.dro_configure_fallout_rules.htm&release=264.0.0&type=5 "Configure rules for how Dynamic Revenue Orchestrator (DRO) handles callouts and auto tasks that fail. Specify how often they're retried, at what intervals, and which queue they go to if they fatally fail.") After you create or update a Fulfillment Fallout Rule, refresh the Fulfillment Fallout Rules decision table. ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_note.png) Note Until you refresh the decision table, DRO reevaluates the previous rule configuration. If no rule matches the step and error code, DRO sets the step status to `FATALLY_FAILED` without retrying it. DRO retries errors that a flow returns through an Auto Task Fault Path. It doesn't retry raw or unhandled Apex exceptions. To make an Apex failure eligible for retry, handle the failure through the flow's Fault Path and return the required Auto Task output variables. See [Auto Task Fulfillment Step](https://help.salesforce.com/s/articleView?id=ind.dro_auto_task.htm&release=264.0.0&type=5 "Use auto tasks to process data automatically as part of your orchestration plan. An auto task fulfillment step requires a Salesforce Flow to perform the automation."). ## Run Time During fulfillment, manage fallout: - Monitor fallout in queues To view fatally failed steps in a specific queue, navigate to the Fulfillment Steps tab and select the Fatally Failed Fulfillment Steps list view. Filter by the Queue column to see your assigned records. See [Monitor Decomposition During Fulfillment](https://help.salesforce.com/s/articleView?id=ind.dro_monitor_decomposition_during_fulfillment.htm&release=264.0.0&type=5 "After a user submits an order to Dynamic Revenue Orchestrator (DRO), you can see how products decompose and can spot issues right away."). - To see steps that have failed, check the fulfillment plan, fallout queues, or the Fatally Failed Fulfillment Steps list view. See [Monitor Decomposition During Fulfillment](https://help.salesforce.com/s/articleView?id=ind.dro_monitor_decomposition_during_fulfillment.htm&release=264.0.0&type=5 "After a user submits an order to Dynamic Revenue Orchestrator (DRO), you can see how products decompose and can spot issues right away."). - Retry callouts and auto task steps, or mark them complete. You can do so one at a time, or in bulk. See [Retry or Complete Multiple Failed Fulfillment Steps](https://help.salesforce.com/s/articleView?id=ind.dro_retry_or_complete_multiple_failed_fulfillment_steps.htm&release=264.0.0&type=5 "From a list view or queue, retry or complete multiple steps at once. If you complete a step in this way, the step ignores any errors that can otherwise stop the completion of the step."). #### See Also - [Monitor Decomposition During Fulfillment](https://help.salesforce.com/s/articleView?id=ind.dro_monitor_decomposition_during_fulfillment.htm&release=264.0.0&type=5 "After a user submits an order to Dynamic Revenue Orchestrator (DRO), you can see how products decompose and can spot issues right away.")