Skip to main content

after all orchstreation items are completed still order is in progress and orchestration in not completed in salesforce vlocity orchestration. 

LastOrchestration Item type is Milestone.  

 

#Vlocity

 

#Flow-Orchestration

 

#Omnistudio  #Order Management

1 Antwort
  1. 24. Sept., 19:05

    A Milestone being the last item is usually the clue here. In Industries (Vlocity) Order Management a Milestone is only a marker: it completes automatically once all of its "Depends On" items are complete, and it never fails, but it does not do any work itself. Completing the milestone does not by itself update the Order record, so an order can sit "In Progress" even though every item on the plan looks green. These are the checks I would go through: 

     

    1. Confirm every item on the plan really is finished. In the orchestration plan view (or by querying the Orchestration Item records for that plan), look for any item that is not Completed, for example Pending, Ready, Running, Failed or Frozen, including items in other swimlanes or in plans of other decomposed/fulfilment-request orders. A single item still pending (often a manual task or a callout waiting for a response) keeps the plan open. 

     

    2. Check that the background processing is running. Orchestration items are progressed by Industries OM asynchronous jobs. Look at Setup > Apex Jobs and Scheduled Jobs for failed or aborted vlocity_cmt jobs and at the debug logs for the user running orchestration. If the jobs are not scheduled or are failing, the plan state is never re-evaluated. 

     

    3. Make sure something actually updates the Order status. Order status normally changes because of an Auto Task in the plan (commonly the asset-creation / order-completion step near the end), not because the last milestone completed. If your plan ends with only a Milestone, add an Auto Task after it (dependency: Depends On the milestone) whose item implementation updates the Order status or runs your standard "create assets / complete order" logic, and re-test with a new order. 

     

    4. For the stuck order itself, once you have found the cause you can retry the failed item from the plan view, or complete the remaining item manually, and the plan should move to Completed. 

     

    References: 

    Understanding Order Management Orchestration Basics (Trailhead):

    https://trailhead.salesforce.com/content/learn/modules/industries-order-management-orchestration-foundations/dive-into-industries-order-management-orchestration

     

    The Industries Order Management Solution:

    https://help.salesforce.com/s/articleView?id=ind.comms_t_the_industries_order_management_solution_229538.htm&type=5

     

    Troubleshooting Industries Order Management:

    https://help.salesforce.com/s/articleView?id=ind.comms_t_troubleshooting_industries_order_management_242806.htm&type=5

     

     

    Assumption: I am assuming this is managed-package (vlocity_cmt) Industries Order Management with a standard plan where the Order status is expected to be updated by a task in the plan. Exact job names and item implementations differ by release and by how your plan definition was built, so please share the state of each orchestration item and whether any Auto Task follows the milestone if the checks above don't resolve it.

0/9000