--- schema_version: "1" id: 3a9f5b35dc5514bedb498928b41a3055a72eac9a4dc1c37d7904d3c9051256c4 title: Monitor Fulfillment During Order Orchestration collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_fulfillment_plan_actions_and_information.md canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_fulfillment_plan_actions_and_information.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: a084f0b222b1817b5c3db67ebffdce98203295b482601311619d17e422aa5970 description: Act on steps or learn more about how the fulfillment process is progressing directly from the orchestration plan. products: - Revenue Cloud release: "264" --- # Monitor Fulfillment During Order Orchestration Act on steps or learn more about how the fulfillment process is progressing directly from the orchestration plan. ### Required Editions
Available in: Enterprise, Unlimited, and Developer Editions
You can see the entire process of an order from the orchestration plan. Search for steps, see their dependencies, and even change their status. ## The Plan as a Whole An orchestration plan shows you the fulfillment steps and their dependencies. You can see at a glance the state of each step, their dependencies, and even whether they're on time. You can quickly see whether a step has finished, is still pending, or has failed. Large orchestration plans load partially with options to add more steps to the plan viewer and to show them everything at once. ![A fulfillment plan with several steps in various states](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_fulfillment_plan.png) ## Plan States Orchestration plans are generated and executed based on the submitted order and their states change as the fulfillment process progresses: - Not Started: The plan has not yet begun. - In Progress: The plan is currently running. - Freezing: The plan is paused but one or more steps in the plan are in progress. You can’t submit in-flight change requests when the plan is in a Freezing state. - Frozen: All steps in the plan are completed or in a Pending state. To amend or cancel an in-flight order, the plan must be in this state. - Completed: The entire plan has successfully finished. ## Search for a Step To find a step, enter a term in the Search field. The step is highlighted and you're brought directly to the term in the plan. You can also zoom the plan in or out, and refresh the plan as fulfillment progresses. To see a list of filtered steps, click ![The View Fulfillment Step Details button](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/icons/dro_filterList_60.png). To filter the steps by category, click a category: - Manual Tasks: Act on tasks or learn more about the upcoming and overdue tasks directly from the order details page. - Fatally Failed - In Progress - Pending - At Risk (this tab appears only if a step is at risk) ## See the Details of the Step Click ![The View Fulfillment Step Details button](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/icons/dro_toggle_panel_right_60.png) on a step to open a panel that shows information about the step. - The Details tab: See general information about the step, including the Execute On rule that defines when the step runs. - The Step Dependencies tab: See the dependencies related to the step. Click a dependency to highlight it in the plan. To highlight a step's dependencies, hover over the step. ## Act on the Step Click ![The Down arrow](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/icons/dro_down_60.png) on a step to see various actions that you can take, such as marking a step as complete, or retrying an auto task or callout. If you can't take an action, then the button isn't available. ## View the Cross-Plan Dependencies Click ![View External Dependencies](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/icons/dro_view_external_dependencies_icon.png) on a step to open the panel showing the External Dependencies tab. See the external step dependencies related to the step. Click a step or plan to open its details page, and take actions such as edit or complete a step. ![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 The External Dependencies icon appears only if there is at least one external dependency. ![Cross Plan Dependencies](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_cross_plan.png) Choose the Cross Plan scope when you're defining the dependency between step groups. See [Set Dependencies Between Fulfillment Steps](https://help.salesforce.com/s/articleView?id=ind.dro_set_dependencies_between_fulfillment_steps.htm&release=264.0.0&type=5 "Connect fulfillment step definitions to create a dependency between them. When an order is submitted, the steps run in the order that you define.") and [Cross-Plan Dependencies](https://help.salesforce.com/s/articleView?id=ind.dro_cross_plan_dependencies.htm&release=264.0.0&type=5 "Cross-plan dependencies establish connections between steps in different fulfillment plans that are part of related orders. Use cross-plan dependencies when a step in one order's fulfillment plan relies on the completion of a step in a different order's fulfillment plan."). ## Fulfillment State Depending on their state, steps are different colors. For example, the green steps are in the Completed state, and the blue ones are in the Pending state. The state of a step is also written on the step. ## The Jeopardy and SLA Clock: ![Blue clock icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/icons/dro_jeopardy_clock.png) The color of the clock indicates whether a step is running on time (blue), late (orange), or is overdue (red). If the step is already completed, then the color indicates whether it was completed on time, in jeopardy, or late. To see more details, hover over ![Blue clock icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/icons/dro_jeopardy_clock.png). ![Information about a step showing that completed in jeopardy of being late](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/revenue/images/dro/dro_jeopardy_info.png) #### 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.") - [Configure Fulfillment Step Jeopardy Rules](https://help.salesforce.com/s/articleView?id=ind.dro_configure_fulfillment_step_jeopardy_rules.htm&release=264.0.0&type=5 "Configure the rules that determine when a fulfillment step is considered to be in jeopardy, and when it's considered late.") - [Set Dependencies Between Fulfillment Steps](https://help.salesforce.com/s/articleView?id=ind.dro_set_dependencies_between_fulfillment_steps.htm&release=264.0.0&type=5 "Connect fulfillment step definitions to create a dependency between them. When an order is submitted, the steps run in the order that you define.") - [Cross-Plan Dependencies](https://help.salesforce.com/s/articleView?id=ind.dro_cross_plan_dependencies.htm&release=264.0.0&type=5 "Cross-plan dependencies establish connections between steps in different fulfillment plans that are part of related orders. Use cross-plan dependencies when a step in one order's fulfillment plan relies on the completion of a step in a different order's fulfillment plan.")