Power Automate New Designer - Item is no longer present in the operation schema

(0) Share

Report

Posted on by uscreyna

Issue: Power Automate designer has been slow loading and recognizing parameters in recent weeks, parameters show a warning that "item '' is no longer present in the operation schema. It should be removed before the workflow is re-saved"

Previous Troubleshooting:

Confirmed this error message is not specific to the SharePoint connector as the operation schema warning appears with multiple actions across multiple flows
When we make a change in the flows, we're unable to save due to this warning, issue goes away on its own if we wait in the designer page long enough
One of Microsoft's Tips in Classic designer vs. modern designer for cloud flows - Power Automate | Microsoft Learn states, "If the saves consistently fail on a specific flow, try opening it in the classic designer and saving there, then returning to the new designer. Learn more in How to switch between the classic and new designer." Confirmed after testing this that we did not get the warning message in the classic designer
Found several community threads from the last few months reporting issues with the New Designer after the latest updates, we're wondering if this error might be a result of a recent change in how the New Designer validates the schema of every action and connection when the flow loads in the canvas, especially since we did not notice this behavior in our tenant until roughly end of April

Has anyone else been seeing issues recently with the New Designer when working with larger flows? Currently our only workaround has been to either wait in the new designer or switch to the classic designer

Categories:

Building flows

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

MS.Ragavendar 7,185 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

@uscreyna,

This is one of the Most common issues which we used to addressed when ever the sharepoint list or sharepoint site is renamed or any updates happened this happened some time refresh the datasource will resolve the issue and some other cases moving between classic vs modern resolves the issue.

You can submit the Idea to Microsoft regarding this - https://ideas.powerautomate.com/d365community/forum/086dd68e-597f-ec11-8d21-0022482e8f9f

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Was this reply helpful? Yes No
uscreyna 2 on at

Like (0)

Report
Copy link

Link copied!

Hello @MS.Ragavendar, we've seen this issue before with SharePoint and previously we could delete and add the action back in to resolve the warning, but this is now occurring with other connectors like Dataverse and the Standard approvals connector. This is also too widespread now that we can't delete and readd every action back into these flows when the issue occurs, this feels more like a change in behavior/performance in larger flows when working with the new designer after April. I will submit an idea to Microsoft as suggested though.

Was this reply helpful? Yes No