Environment Variables suddenly not found

(1) Share

Report

Posted on by abc 123

789 Moderator

There are 3 environment variables (EV) used across about 5 different Flows. One of the three EV stopped being "found" by one of the Flows, and a second EV in an additional Flow. To resolve, the environment variables had to be swapped out for their literal values, and then the Flow would operate normally again. (It took multiple times to save, as it would completely freeze during the Saving process.)

Needless to say, this is complete garbage, and the half-baked pie that is PowerAutomate never misses an opportunity to make programmers look bad. Nothing like having the Boss breathing fire on me while coffee is still being brewed.

Question: What is causing this, how can it be prevented (besides NOT using them), and when will we know that this has been addressed by Microsoft and won't happen again?

Thanks for nothing interns.

P.S. The "Categories" selection below is 100% useless.

Error:

InvalidTemplate. Unable to process template language expressions in action 'Calc_OCC' inputs at line '0' and column '0': 'The workflow parameter 'envDSSI_numSIAdminGrp (new_env_DSSI_numSIAdminGrp)' is not found.'.

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

AnthonyAmador 2,553 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi,

This is probably related to the network infrastructure issues Microsoft experienced on 7/30/2024, which also impacted Power Platform.

Are the environment variables still there but not recognized? If you can replicate the issue, I’d suggest opening a ticket with Microsoft Support and pushing them to investigate the issue so you can provide an explanation to your boss.

In case the solution was not managed, I recommend continuing to use a managed solution for production, in case this was caused by another user’s human error.

Cheers.
Anthony.

Was this reply helpful? Yes No
abc 123 789 Moderator on at

Like (0)

Report
Copy link

Link copied!

Still failing today, but in a different Solution. I don't know the difference between a managed and non-managed solution, but do know that no human has touched the Environment Variables.

Was this reply helpful? Yes No
Suggested answer

CU16121824-0 2 on at

Like (0)

Report
Copy link

Link copied!

Super late, but I had this same issue and resolved by switching to the old editor and remaking all the references to the environment variables.

No idea why that works, the underlying code view didn't change. lol.

Was this reply helpful? Yes No
Suggested answer

abc 123 789 Moderator on at

Like (0)

Report
Copy link

Link copied!

There's no excuse for needing to recreate these variables, nor ever having them expire. They should be etched in stone. If they're just a flippant experiment, then warn the programmers of that, and we'll NOT use them.

Was this reply helpful? Yes No