2 years ago, I wrote about how to re-enable a flow after it has been automatically disabled because it hasn’t been running for 60 or 90 days.

For the last 2 years, this worked flawlessly. But today, my flow failed.

In this short follow-up post, I will explain how to fix this.

Why did it stop working?

Microsoft loves changing things around and so they did. In the previous email that was send to the owner of the flow (subject: Alert! Your flow has been turned off since it was not running), the URL behind the ‘Go to my flow‘ button was just a simple string like this:

https://flow.microsoft.com/manage/environments/<ENVIRONMENT ID>/flows/<FLOW ID>/details/...

from which you could easily extract the Environment ID and the Flow ID.

But now, Microsoft has decided to change the format of that URL with encoded characters, like this:

https%3A%2F%2Fflow.microsoft.com%2Fmanage%2Fenvironments%2F<ENVIRONMENT ID>%2Fflows%2F<FLOW ID>%2Fdetails%2F...

So now, we cannot identify the Environment ID by splitting on the ‘https://flow.microsoft.com/manage/environments/‘ string.

Also, Flow ID cannot be identified anymore by splitting on ‘/flows/‘.

How to fix this?

Luckily, the solution is quite simple. You can add an action above your Initialize variable actions in which you replace the %3A character back with ‘:’ and the %2F character with ‘/’.

In my case, I added a Compose action with the following expression:

replace(
	replace(
		triggerOutputs()?['body/body'],
		'%3A',
		':'
	),
	'%2F',
	'/'
)

This replaces all occurrences of ‘%3A’ and ‘%2F’ in the body of the email with ‘:’ and ‘/’ so you will have a normal URL again.

After this, you simply replace ‘triggerOutputs()?[‘body/body’]‘ in the expressions of both your Initialize variable actions with the Dynamic content reference to your compose action and your flow should be working fine again!

Future

Keep in mind that Microsoft is still in the transition from the old Microsoft Flow URLs to the new Power Automate URLs.

So there is a chance that in the near future, this flow configuration must be altered again, because it is still using the old Microsoft Flow URLs in the notification email.