Some Order Lines Stuck in Shipped Status in Cloned Environment
Summary:
We are investigating an Order Management orchestration issue in a cloned environment and would appreciate feedback from anyone who has encountered similar behavior. We have shipped an order and Line 1 progressed as per expectation and was successfully invoiced however line 2 and 3 are stuck at shipped.
Content (please ensure you mask any confidential information):
Environment Context
This is a cloned environment.
Oracle Support has indicated that after a clone, existing orchestration instances become stale and are not expected to continue processing normally. According to Oracle, all existing order orchestration become stale and should not be progressing through the remaining orchestration tasks, including invoicing. However we have observed a different behavior which we would like to further understand and if others have also encountered similar issues. We would like the existing orders be available to be processed further as it becomes easier to debug existing production issues.