Issue with Flow Designer: Updates Not Reflecting in Subsequent Steps Intermittently

[Noura]

Hi everyone,

I'm encountering an issue with a Flow where I'm updating multiple attributes on a user record in one step via action update record, and while the step is marked as complete, the updated values are not always reflected when the flow moves to the next step. This issue is intermittent, meaning it doesn’t happen consistently.

I suspect that the issue might be related to asynchronous behavior in the flow — possibly the updates aren't fully committed before the next step is executed. Has anyone encountered similar issues, or can anyone suggest best practices to ensure that updated values are consistently reflected before moving on to the next step?

Any insights would be much appreciated!

Thanks in advance!

[Ankur Bawiskar]

@Noura 

which field it's not updating? did you identify the pattern?

Any before update business rule is blocking the update of those specific field?

what debugging did you perform?

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Noura]

Hi @Ankur Bawiskar ,

Thank you for your quick response!

While testing the action (with test button on the sublflow), the problem doesn't appear. However, when running the flow automatically, I noticed that the record is updated (the fields are populated correctly), but in the action right after the update, the record still points to the old values. And this is not always happening.
When I added a delay of 2 seconds between the update and the next step, the issue did not appear, and the correct values were retrieved. However, when I increased the number of fields being updated in the same step, the issue occurred again. This makes me suspect that the action of update might not be fully committing the updates before moving to the next step, especially when multiple fields are updated.
That's why I need expert advices and best practices to undestand and deal with this case.

Best Regards,

Noura

[Ankur Bawiskar]

@Noura 

yes that's correct then, it's getting reflected with the old values and getting delayed.

I haven't encountered any such thing.

If my response helped please mark it correct and close the thread so that it benefits future readers.