Power Platform Community Forum Thread Details

I query odata and check if I can update an existing row or that i should add a new row.

Afterwards it checks for all rows in my sharepoint that have both value "X" in column A and 1 in column "Email_send". If this is the case it generates an email that is than send to my emailbox. If there are no rows for which this is true, no email will be generated and send.

Email_Send is an extra column that is not updated based on the api data, but a column that i use to check if i have already send an email for a certain row. I update this row with the power automate flow (not visible in the picture)

Now the problem is the following: The flow works, the email gets send based on the filter query. However the flow is run everyday and most of the time there are no changes to the data, but sometimes I do receive an email, which means that the filter query is true. I could go 5 days with no changes to the data and i would receive an email again and than 4 days later, again an email, etc.

When I check on my flow I do receive the following error message that dissapears after a few seconds "Item/Email_Send" is no longer present in the operation schema. It should be removed before the workflow is re-saved".

It dissappears when the site adress and the list name of the sharepoint list are loaded.

How can i change my flow in such a way, that the random emails no longer happen?

Categories:

Building flows

Hi! The warning message you're seeing — "Item/Email_Send is no longer present in the operation schema" — is the key to your problem. Here's what's happening.

Root cause: Schema mismatch

Power Automate caches the SharePoint list schema at design time. When a column is renamed, deleted, or its internal name changes, Power Automate's cached schema drifts from the actual list. When the schema is out of sync, filter queries can behave unpredictably — Power Automate may execute the step without the filter applying correctly, meaning all rows pass the filter and emails are sent unexpectedly.

How to fix it

Open the flow in edit mode and find the step referencing Email_Send.
Remove and re-add the SharePoint action — this forces Power Automate to re-fetch the current list schema.
Re-select your filter column from the refreshed schema dropdown.
Save and test to confirm the filter works correctly.

Per Filter and copy data – Microsoft Learn, OData filter queries must use the column's internal name. If the internal name of Email_Send changed, update your OData query accordingly (e.g., Email_Send eq 1).

Prevent recurrence

Use the OData filter query syntax directly (e.g., Email_Send eq 1) rather than the visual filter builder — the query string persists even if the visual schema drifts.
Periodically re-save flows that reference SharePoint columns to refresh the schema cache.

References

Found this helpful? Please mark ✅ "Does this answer your question?" so others searching for the same issue can find it quickly. A 👍 on "Was this reply helpful?" or a ♥ Like is also much appreciated!

Raghav Mishra — LinkedIn | PowerAI Labs