Flow Designer showing empty runtime values for different fields after Xanadu Update

harshhkumar
Tera Contributor

Recently our instance was upgraded to the Xanadu version but after that the Flows are not working correctly. The value of some fields of trigger record in some actions are coming as empty even though I know they are not empty. 

At the first step, there is a subflow which is updating a field on the trigger record, there is a wait until completion condition for that step. After the first step, the next few steps are if and if else condition related to the field which is modified in step 1, but the if and if else conditions are failing because they are showing empty runtime value for that field. This doesn't used to occur earlier, it only started after the Xanadu update. This is just 1 example, this issue is occurring for other fields as well which I am modifying as part of this flow. When I look at the XML of the record, I can see the fields are not empty.

5 REPLIES 5

The only thing that worked for us was reverting back the flows to engine major version v1, after xanadu/yokohama upgrade, flows were updated to engine major version v2.