Errors across flows

(0) Share

Report

Posted on by JonSandersen

Hi,

We started seeing these kind of errors across flow on Friday without have changed anything related to the failing fields.

Have anyone else experienced this or know how to handle it?

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Suggested answer

Srini007 3,483 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @JonSandersen,

Make sure that your connections are connected and stable, you can check this from Myconnections, also ensure that the connection for the action is correct, then you need to check the dataverse table and check if the columns are present or any changes you identified. This way you can spot the issue, If not please let us know with more details

Please ✅ Does this answer your question if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider answering Yes to Was this reply helpful? or give it a Like ♥

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!
This error occurs because your flow is referencing outdated or invalid schema fields

Fix:

Delete & recreate affected action

Refresh connection

Validate Dataverse fields

Was this reply helpful? Yes No
Suggested answer

Vish WR 3,748 on at

Like
a
(0)

Report
Copy link

Link copied!

@JonSandersen

As you mentioned, without any changes, the flows were giving an error. I would strongly recommend checking the M365 health center in your tenant to see if there are any incidents related to his for the Power Platform services and Power Automate services

As mentioned by @Srini007 first check the connection status to ensure the connection is not in a failed state due to any credential change/expiry. if connection is failed, re-establish the connection

Also, if you have unified support, please raise the case with Microsoft and reach out to CSAM as well. If you are raising a ticket with microsoft dont fix all flow by creating the connection etc. Have a few samples for Microsoft to troubleshoot and find the root cause. This is important as you mentioned, there is no changes to the flow, and you experience something suddenly

Was this reply helpful? Yes No
Suggested answer

Riyaz_riz11 4,204 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi,

Microsoft pushed an update on their end it might be the issue, so better to remove the flagged fields that are showing as missing, then re-add and re-map them manually. I think this is the best quickest fix to get the flow working again.

Note: Save a copy before touching anything before you start fixing.

If I have answered your question, please mark it as the preferred solution ✅ . If you like my response, please give it a Thumbs Up 👍.
Regards,
Riyaz

Was this reply helpful? Yes No
JonSandersen 5 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi,

Thank you all for the replies.

Even though there was nothing wrong with the connection references, for some reason it still worked just to change to new ones on at least some of the flows so far.

There is no issue with the schema fields either, so my guess is that is was the Microsoft update that triggered it for whatever reason.

Anyway, thank you for your help!

/Jon

Was this reply helpful? Yes No
Vish WR 3,748 on at

Like
a
(0)

Report
Copy link

Link copied!

@JonSandersen

Thanks for the updates .

Was this reply helpful? Yes No