Task status not applicable in order orchestration process
Summary:
Hi,
I am using an orchestration process which is having a reserve task. Usually reservation task status is ok but sometimes for same orchestration process says "Not applicable" when there is not enough stock.
Order instead of failing and giving an error due to lack of stock, it moves forward to awaiting shipping.
Why?, has anybody seen this status not available? See screenshots below.
I have checked MOS notes and check the "Line-Selection Criteria" but cannot see anything wrong. Item is reservable and shippable. Any ideas?
I have also deployed again the orchestration process and same behaviour
Content (please ensure you mask any confidential information):
Tagged:
0