Power Automate — Variable Values Replaced with Empty Strings

(1) Share

Report

Posted on by Kankamon02

Hi,

We're experiencing a serious issue where all variable values in our Power Automate flows are being replaced with empty strings, which causes the flows to fail. This is happening across my entire team everyone using Power Automate is affected.

Is anyone else seeing the same problem? This is causing significant business impact for our organization, as we have over 100 flows running across multiple environments.

Here some of the example from screenshot

Categories:

General topics

I have the same question (0)

All responses (10)

Answers (0)

Sort by

Suggested answer

Vish WR 644 on at

Like (1)

Report
Copy link

Link copied!

as you mentioned it happens for all i would recommend raise a support ticket and also checkout health center for any service incident

Was this reply helpful? Yes No
Suggested answer

Haque 1,758 on at

Like (1)

Report
Copy link

Link copied!

Hi @Kankamon02,

Probably the root cause appears to be a platform-level bug or regression affecting variable handling in Power Automate flows. Users across organizations report that variables lose their values unexpectedly during flow execution, resulting in errors and failed runs.

This issue is actively discussed in the Power Platform community forums, and Microsoft is likely investigating it given the scale and severity. Meanwhile, affected users experience critical operational impact, especially those with large numbers of flows relying on variables for data processing.

Without delay - can you please open support ticket so that it is addressed asap?

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Kankamon02 27 on at

Like (2)

Report
Copy link

Link copied!

Thanks for you replied, I already opened the support ticket. Now I know that it doesn't heppend only with my org but other also facing similar issue.

Now we're fixing our flows to let it continue working

Was this reply helpful? Yes No
Vish WR 644 on at

Like (0)

Report
Copy link

Link copied!

hope you find the root cause , share here if you know the root cause

Was this reply helpful? Yes No
PhillipConrado 10 on at

Like (4)

Report
Copy link

Link copied!

I’m facing the same issue here. In our case, it only happens while editing the flow. It seems that if you apply a quick fix and save the flow before it finishes loading completely, the values are lost.

In my organization, I manage around 150 flows. We also tested this behavior in another environment, and the issue still persists. We noticed that only flows where a quick edit was made are affected.

Important: If you wait until the flow is fully loaded before saving, the values are preserved.

Please see the screenshot below. You can notice that until the full load is completed, the connector properties are not displayed correctly, which seems to be related to the issue.

Was this reply helpful? Yes No
JC-10040355-0 4 on at

Like (1)

Report
Copy link

Link copied!

Agreed, if you open a flow, then watch network activity, ant wait till it to die out to a trickle of one every 10/15 seconds then its "loaded" and you seem to be SAFE to save.

This is extremally frustrating, they have obviously implemented some kind of lazy loading enumeration through the flow, but they dont show any indication on the page of the % of entire flow context that is loaded.

so if you have something quick to do in a flow, and you go in, make the change quickly and save, you likely end up with a completely broken flow with all kinds of data missing. It is really unacceptable for a production that we continue to be "beta" tested on changes to the new view.

Was this reply helpful? Yes No
NeB-tk 10 on at

Like (1)

Report
Copy link

Link copied!

It was quite time-consuming to restore variable values after switching from "New Designer" to "Old Designer." The transition was necessary due to performance concerns, such as memory errors experienced with "New Designer." These issues suggest that "New Designer" may require further refinement. Perhaps it's better to avoid making CoPilot a universal solution and instead allow developers to use it as a tool rather than the answer to everything—just my opinion.

Was this reply helpful? Yes No
JK-07011237-0 2 on at

Like (0)

Report
Copy link

Link copied!

I'm experiencing the same. Oddly, I did NOT switch from new to old or vice versa, but the system decided to switch my flows to new view all on its own when I opened the flows. It also did the same with the copies of the flows I created, so making a copy did me no good and didn't provide any sort of safety net!

This occurred with BOTH the flows I opened today - I wasn't even actually editing either flow but needed to open them to see the details of some steps to duplicate them for a new flow. PowerAutomate is supposed to make our jobs easier - not harder. I do not have time to troubleshoot and correct every flow I open. The system needs to be reliable. Looks like it's time to start looking elsewhere for our automations.

Was this reply helpful? Yes No
Suggested answer

Vish WR 644 on at

Like (0)

Report
Copy link

Link copied!

Edited:
Posted wrongly, not able to remove the suggested answer

Appologise

Was this reply helpful? Yes No
Haque 1,758 on at

Like (1)

Report
Copy link

Link copied!

All- Would appreciate if you guys post here the updates when MS resolve this issue.

Was this reply helpful? Yes No