---
schema_version: "1"
id: a9ecea6d9fa936c341cb4182d3dcf49eb65094871c07bc7fafb474e4c9639865
title: Retry Assetization for a Dynamic Revenue Orchestrator Order
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_retry_assetization_for_an_order.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_retry_assetization_for_an_order.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 97749aad4af7121dcd04d7eae4a2a2d03ab7af111c52c51f13b36cb133669896
description: If assetization doesn't complete after fulfillment, fix the cause of the failure and invoke the Create or Update Asset from Order action. The action retries commercial assetization for the order and starts technical assetization to create or update its fulfillment assets.
products:
  - Revenue Cloud
release: "264"
---
# Retry Assetization for a Dynamic Revenue Orchestrator Order

If assetization doesn't complete after fulfillment, fix the cause of the failure and invoke the Create or Update Asset from Order action. The action retries commercial assetization for the order and starts technical assetization to create or update its fulfillment assets.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d29419e63">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d29419e63 ">To create or update assets from an order:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d29419e63 ">
              <p>The Assetize Order permission set from the Revenue Lifecycle Management
                permission sets.</p>
              <p style="margin-bottom:0;">The user who submits an order needs this permission set so products are assetized
                automatically upon fulfillment. See <a href="https://help.salesforce.com/s/articleView?id=ind.dro_permission_sets_in_dynamic_revenue_orchestrator.htm&amp;release=264.0.0&amp;type=5" title="Permission sets extend the user's functional access without changing their profiles and are the recommended way to manage permissions. Dynamic Revenue Orchestrator (DRO) provides standard permission sets for administering DRO, designing fulfillment, managing fulfillment at run time, and submitting transactions. Assign the permission set that matches each user's role.">Permission Sets in Dynamic Revenue Orchestrator</a>. This
                requirement also applies to users, integration users included, who invokes this
                action directly for recovery. The same permission set apply to direct API
                calls.</p>
            </td>

          </tr>
        </tbody>
      </table>

During commercial assetization, Salesforce creates or updates assets from the order line items. During technical assetization, Dynamic Revenue Orchestrator (DRO) creates or updates fulfillment assets from the fulfillment order line items.

Use this procedure when the fulfillment plan has completed but the order's Orchestration Submission Status is Assetization Failed. Also use it when Salesforce or DRO didn't create the expected assets or fulfillment assets. For the meaning of other order statuses, see [Order Submission to Dynamic Revenue Orchestrator](https://help.salesforce.com/s/articleView?id=ind.qocal_order_submission_for_fulfillment.htm&release=264.0.0&type=5 "Submit sales transactions to Dynamic Revenue Orchestrator (DRO) for fulfillment by using the Submit Sales Transaction invocable action in flows or Apex classes. Automating this process via record-triggered flows makes sure that all eligible records enter the fulfillment pipeline immediately upon meeting specified criteria. Customizing order page layouts to include Orchestration Plan and Orchestration Submission Status fields provides users with real-time visibility into the fulfillment progress."). Before you retry assetization, correct the configuration, data, permission, or status issue that caused the failure.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-revenue-264-0-0-production-enus/91ca99c6-d5c8-4986-b961-c6b7801e0d0d/images/icon_important.png)

Important Don't invoke Submit Sales Transaction to retry assetization for an order already submitted for orchestration. The action validates the order's Orchestration Submission Status before doing any work and always rejects the resubmission with the DRO\_ORDER\_ORCH\_SUBM\_STATUS\_INCOMPATIBLE\_ERROR error to prevent creating a duplicate fulfillment plan. This rejection applies whether the status is Completed, Assetization Failed, or Submitted.

![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 Retry action for a failed fulfillment step doesn't retry assetization after the fulfillment plan is complete. 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.").

1. On the order record, confirm that Orchestration Submission Status is Assetization Failed.
    
    If the field isn't on the record page, add it to the Order page layout.
2. Identify the failed phase and correct the cause of the failure.
    
    Assets created from order line items appear on the Assets tab of the related account. Fulfillment assets created from fulfillment order line items appear in the Related Tab's Fulfillment Asset section.
3. Send a POST request from an authenticated REST client to the Create or Update Asset from Order standard action.
    
    ```
    /services/data/vXX.X/actions/standard/createOrUpdateAssetFromOrder
    ```
    
    In the request body, replace ORDER\_ID with the ID of the order to assetize. The order must be in the Activated state. The action rejects the request for an order in any other state.
    
    ```json
    {
      "inputs": [
        {
          "orderId": "ORDER_ID"
        }
      ]
    }
    ```
4. Review the action response to confirm that DRO accepted the request.
    
    Commercial assetization runs before technical assetization. Technical assetization can continue asynchronously after the Create or Update Asset from Order action returns.
5. Wait until Orchestration Submission Status is Completed and verify that DRO created or updated the expected assets and fulfillment assets.
    
    DRO sets the status to Completed after commercial and technical assetization complete successfully.

If commercial assetization already completed successfully for the order, invoking the Create or Update Asset from Order action again doesn't rerun technical assetization.

After the retry, check the existing Fulfillment Asset for these problems.

- It's inactive.
- Its quantity is zero.
- It's missing its expected relationship to the Asset.

If you see any of these problems, contact Salesforce Support before retrying again.