cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Resolver II
Resolver II

Saving Flows... getting "Encountered internal server error."

When trying to save any existing Flows we are getting "Encountered internal server error. Tracking ID is "".

We've tried using different accounts and different browsers to no avail.

 

As a side note, we encounter the same error trying to connect to existing data connections in PowerApps.

Thanks,

Shane

 

4 REPLIES 4
Highlighted
Solution Sage
Solution Sage

Re: Saving Flows... getting "Encountered internal server error."

Hi @shanemeisner ,

Does the issue still exist?

Here's an update from Flow Support, please take a reference here:

https://us.flow.microsoft.com/en-us/support/

Please feel free post back if you need more help.

Best Regards,

Community Support Team _ Zhongys

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

 

Highlighted
Resolver II
Resolver II

Re: Saving Flows... getting "Encountered internal server error."

Thanks for the reply.

The issue does still exist for our environment and I have opened a support incident with Microsoft.

They think it might be related to what apps are in what Data groups in the Data Policy settings for Flow.

Highlighted
Solution Sage
Solution Sage

Re: Saving Flows... getting "Encountered internal server error."

Hi @shanemeisner ,

Thanks for your feed back.

If there is anything else we can do for you, please feel free to post in the forum.

Best Regards,

Community Support Team _ Zhongys

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Highlighted
Resolver II
Resolver II

Re: Saving Flows... getting "Encountered internal server error."

to a Fix Microsoft implemented, here is what they sent:

 

Our connectors use two different ID formats. Previously, our data loss prevention policies only recognized one and not the other. We asked the DLP admin to add both formats as a workaround.

After this bug was fixed, the policy considered the two ID formats to be duplicates of each other.

Normally, this duplicate blocking would be correct, but we failed to account for the duplicates created by the workaround.

To resolve the issue, we manually edited the Save request to remove one of the duplicate values.

Helpful resources

Announcements
firstImage

Now Live: Power Virtual Agents Community!

We are excited to announce the launch of Power Virtual Agents Community. Check it out now!

firstImage

New & Improved Power Automate Community Cookbook

We've updated and improved the layout and uploading format of the Power Automate Cookbook!

thirdimage

Power Automate Community User Group Member Badge

Fill out a quick form to claim your user group badge now!

Top Solution Authors
Users online (7,486)