CoE - Changed environment url

[LimeLeaf]

Dear community,

i changed the environment url of my COE enviorment after importing the COE Solution.

Before i changed the environment url everthing was working fine, now a lot of COE flows are failing with the following error: 

(Http request failed with status code 'NameResolutionFailure' and status message: 'The remote name could not be resolved: )

The url he is trying to resolve here is the "old" url that was right before i changed the environment variable in the power platform admin center for the COE environment.

It looks like he is pulling in the old environment url here from a source that i am not aware of. I searched for the 
"Environment" Table of the COE Solution but also this one contains the right new url.

Any idea where to change the URL so that the COE is pulling in the right one and get rid of the old URL? 🙂

[PowerPuffKK]

Hi @LimeLeaf ,

Unfortunately you will find that all CoE components will be calling the old URL in various flows etc. so changing it within one flow only will not work.

When you say you changed the environment of your CoE, do you mean you installed it again in your new environment? Or what exactly did you want to change (and why)?

[LimeLeaf]

Hi @PowerPuffKK,
 
and thanks for your reply.

I changed the environment url of my COE environment. 
It's one of the propertie every environment has, which can be changed after you created an environment.
Here you find some more information: (https://docs.microsoft.com/en-us/power-platform/admin/edit-properties-environment)

You are not changing the url directly in each flow which is running inside of the CoE Solution, the individual flows are retrieving the environment url from somewhere inside the COE solution. My question here is where those environment url are stored inside of the url tables, so i can update it. In fact there is a Table called Environment (admin_environment) in the COE solution where environment variables and the url is stored. But it seems like this is not the correct one where the url is pulled in from for the most flows.

Coming back to your question why i changed the url:
We got spicific interal restrictions how the url of a environment has to be named, this is the reason why i changed it. It was simply forgotten to align to this restrictions during the creation of the environment. 

[LimeLeaf · Accepted solution]

Dear community,

I found the solution to my problem.

Simply turn off all COE cloud flows and cancel any running instances of them. Afterwards turn on each of them again and run them in the order as described in the COE implementation guide. (https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components)

Seems like a turn off and a turn on of the flows makes them recognize the change of environment url.

After this all my COE cloud flows are running fine again.

I learned it the hard way now. It's much easier not to change the url of the environment to avoid turning on and off each flow of the COE again. 

Hope that helps anybody running into the same issue.

[IhnoHanuschka]

Thanks for posting your solution - we just ran into the same issue and could fix it quickly now!

[LimeLeaf]

Thanks @IhnoHanuschka I'm happy to hear that this helped you out.
Please consider to mark my post as "Accept as Solution" as it would make it more accessible to others with the same problem. 🙂

[IhnoHanuschka]

Hi @LimeLeaf - I wanted to do so but this option didn't show... maybe you can only do that as creator of the post.

[LimeLeaf]

You are totally right! I forgot that I answered my own question here. 🙂