OOB Fulfilment Policy decision table does not trigger the sub flow despite matching conditions

[SamruddhiS]

OOB Domain Order Fulfilment Policy decision tables is not triggering a sub-flow even though the conditions are met post upgrade from Vancouver to Washington dc.

Below OOB Decision Table Policies we are using to trigger sub-flows for each domain order based on a requirement. We recently upgraded from Vancouver to Washington DC release. Decision Policy table has correct conditions set-up for each specification. Despite meeting the conditions, sub-flow is not getting triggered for some domain orders and the same sub flow is triggering for other domain orders within same customer order.

Decision Policy - Product Order Fulfilment Policy
                             Service Order Fulfilment Policy
                             Resource Order Fulfilment Policy

When I try to test Decision Table by clicking 'Test' button, it returns correct name of the sub flow as output. Even sub-flow execution works fine when I test it manually by passing domain order # hence I am unable to figure out where the issue is. Also same sub flows is triggering fine for domain order with 'Prod Spec A' but it is not triggering for domain order with 'Prod Spec B'

Has anyone faced similar issue at any point? 

[Tilottama Nande]

Yes, we are also facing same issue. post upgrade to Washington release working decision table entries not triggering respective subflows.. We have not found any solution yet.