Flow Designer showing empty runtime values for different fields after Xanadu Update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2024 11:31 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2025 12:34 PM
Facing same issue, do you have any update on this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2025 09:20 PM
Same issue happening did you get any workaround?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-28-2025 03:22 AM
We raised a HI ticket for this, the support team went through it and were convinced that there is an issue on there side. They have raised a Problem Record for it and hopefully it will get fixed in any of the patch updates.
For a workaround, you can try using a look up record after you have used a update record action. I know this might not be the best solution, but this works for us as of now. @kinneraS @shibinmonjoseph
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2025 09:50 AM
Having the same issue. Runtime values are missing on the first action in the flow causing the next flow logic to evaluate as true skipping the approval conditions then completing the flow. I tried adding a look up action after the Get Catalog Variables action, this didn't work. I also tried adding a look up action as the very first step in the flow, this also didn't work, the Runtime values are still missing on the Get Catalog Variables action which is the first action in the flow.
The flow already has a look up action after an update record action. Is there another workaround?
