Dynamics 365 (CE) - Flows Failing in restored environment

(0) Share

Report

Posted on by aKnowledgeWorke

Hi,

We have Dynamics 365 CE (current ver 9.2.x). Our solution has 16 "cloud flows" (Power Automate flows).

I recently restored Production back into our Training environment, and all flows were "off". Turning them back on generated an error ("unexpected error"). If I look at the individual flows, they show as having no connection references. Editing the Dataverse connection step with a known good account and trying to save it generates:

Request to XRM API failed with error: 'Message: An unexpected error occurred. Code: 0x80040216 InnerError: '.

The account and credentials are definitely correct. I have tried swapping credentials to another sys admin account and trying to save - no success there either. My understanding is that all the dataverse (and legacy Common Data Service) connections referenced the current environment by default, so I don't understand what's going on. There are multiple connection references in the Default Solution for the same (service) account, but this doesn't seem to have caused issues previously in other environments.

Can anyone help?

cheers,

Steve.

Categories:

Using connectors

All responses (2)

Answers (1)

Sort by

Verified answer

v-jefferni Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @aKnowledgeWorke ,

Based on the thread below, you may be able to get the flow to run after enable the administration mode of this environment:

https://powerusers.microsoft.com/t5/Using-Flows/Power-Automate-Flow-Triggers-not-working-Common-Data-Service/td-p/741182

According to this blog:

https://crmtipoftheday.com/1351/flows-not-triggering-after-an-environment-copy/

Hope this helps.

Best regards,

Community Support Team _ Jeffer Ni
If this post helps, then please consider Accept it as the solution to help the other members find it.
aKnowledgeWorke 11 on at

Like
a
(1)

Report
Copy link

Link copied!

thank you!. I also found that Publishing All Customizations worked. I suspect both actions generate some kind of reset for the environment...
Steve.