Views:

Applies to Product - Dynamics 365 Intelligent Order Management


What’s happening?
Customers are experiencing issues with orchestration flows in Dynamics 365 Intelligent Order Management (IOM). Common symptoms include: - Orchestration flows failing to publish with the error message "Failed to publish the journey." - Orchestration actions getting stuck or not progressing automatically. - Orders being directed to different warehouses despite being in stock at the same location.
 

Reason:

  • The orchestration flow may be encountering errors due to invalid records in the FulfillmentSource, which can lead to exceptions such as "unable to validate transitions for entities."
  • Specific Legal Entities may be affected, causing all orders within those entities to fail.
  • The presence of filter policies that reference other components may prevent the unpublishing of journeys, leading to the error "workflow is referenced by other components."

 

Resolution:

  1. For Publishing Issues:
  2. If encountering the error "Failed to publish the journey," follow these mitigation steps:
    • Unpublish journeys referencing the policy.
    • Remove filter policy references from the unpublished journeys.
    • Save the journey.
    • Navigate to the Maker Portal - Solutions - Default - Cloud Flows.
    • Check for any Power Automate flows with the naming convention journeyId_step_stepname. If found, delete them.
    • Attempt to unpublish the policy.
  3. For Stuck Orchestration Actions:
  4. Review the orchestration flow configuration to ensure that all steps are correctly set up.
  5. Implement retry logic for actions that are not progressing automatically.
  6. If the issue persists, consider removing the installed provider and reinstalling it, ensuring to clean up any instantiated objects by IOM before reinstalling.
  7. For Orders Directed to Different Warehouses:
  8. Check the strategy configuration for constraints. If using "Restrict partial fulfillment of orders constraint," consider changing it to "Limit number of warehouses per order line constraint" to see if the expected behavior is achieved.
  9. Ensure that the setup for FRO (Fulfillment and Returns Optimization) is correctly configured with inventory visibility.
  10. General Troubleshooting:
  11. If the orchestration flow is not functioning as expected, check for any recent updates or changes in the environment that may have affected the orchestration logic.
  12. Gather detailed logs and error messages from the orchestration step summary results to assist in further troubleshooting.
If the above steps do not resolve the issue, further investigation may be required, and it may be necessary to escalate the case to the engineering team for additional support.