Synchronous subflow from script has wrong context in WDC patch 3 and patch 4 (Scoped)

[B01lt]

This just broke with patch 3 and is also not working in patch 4:

Within a scoped app, calling a synchronous subflow from a script where the subflow performs database operations. 

The result is operations performed within the subflow will carry over the context (current) from the origin source.

example: A record producer calls a subflow where adjacent records are inserted and given back to the RP. Business rules that run on the adjacent records run in the context of the record producer resulting in failure. 

I have a HI ticket and there is an existing problem PRB1763535.

Beware of these 2 patches if you use scoped apps and subflows. 

[B01lt]

KB1646316 is the known issue that states the fix will arrive with patch 5.

We found a workaround by running a before insert business rule on the produced record and kicking off the subflow/logic there. This allows the subflow to run in a new thread.