Accessing a record within a flow does not work after the plan runs on MID - Known Error

Accessing a record within a flow does not work after the plan runs on MID Description Dot walking off a record (accessing a field from a related record) works before calling the mid and fails after calling the mid.

It could be that this causes the flow to get stuck and not proceed or it could be that a pill passed to an Ask for Approval evaluates to an empty string and approvals are not created and the approval action is skipped.

Steps to Reproduce

Steps:

1. Configure a MID server on a Paris release instance. 2. Import the attached the update set - sys_remote_update_set_ActionToReprodueTheIssue.xml 3. Run "ActionWithMIDAndWaitCondition" action in Flow Designer. Note: Both 1 and 3 Script steps are congiured to run on MID. 4. Enter "1" as the input.

Expected Result: The action should run and complete properly.

Actual Result: Wait For Condtion is not triggered properly after running the plan on MID so the action hangs at the Wait For Condtion step and the action stays in Waiting status. This issue does not happen if change the 3 Script step is configured to run on Instance.

Workaround Retrieve the fields in the flow prior to going to the MID