Power Platform Community Forum Thread Details

I have a SharePoint get items action that has previously been working (for months). There has been no changes on my end, but for some reason this month it stopped working. By stopped working I don't mean an error, it just keeps returning null and there is stuff for it to grab. I recreated the get items and that appears to work, but I don't want to have to do that with all my actions. Has anyone else experienced something like this or know how to fix it without rebuilding the actions? I tried copying it, changing and saving one filter at a time and it constantly comes back as null. Please help!

Categories:

Building flows

Hi @NR-07101917-0,

I have not run into this precise behavior before, so let me frame a few checks that usually surface the root cause.

The signature you describe, worked for months, no changes on your side, now returns null with no error and a successful run, points almost always to the list crossing the 5000-item view threshold. Past that limit, Get Items stops returning matches on non-indexed columns, and it does so silently. The run reports success. That is by design, not a bug, which is why recreating the action seems to help. The new action starts with different pagination and top-count defaults, so it masks the real issue until it resurfaces.

A few things worth validating before you rebuild everything:

Confirm the item count in the list. If you are over 5000, that is your answer. This is the first thing I check.

Index the columns used in your Filter Query. List Settings, Indexed Columns. Equality filters on indexed columns keep working beyond the threshold. This is the durable fix, not a workaround.

Enable pagination on the Get Items action. Settings gear, Pagination On, threshold set above your row count. Pair it with an indexed filter to pull the full set reliably.

Drop any Order By on a non-indexed column. Sorting past the threshold returns empty results in the same silent way and catches a lot of people out.

Diff your rebuilt action against a broken one. Line up Filter Query, Top Count, pagination, and Order By. The delta shows the exact setting to patch, so you correct the existing flows instead of recreating each.

If the list is under 5000, the threshold theory does not hold, and the likely culprit is a stale schema cache from a renamed or retyped column, where the Filter Query references an internal name that no longer resolves. That returns null rather than erroring.

There is also a search indexing angle worth ruling out. Newly created items are indexed on a delay, and if anything is caught in a reindex or the column was recently added, the new rows will not surface in filtered results until indexing completes. Worth confirming the timing of when the new items were added versus when the flow ran.

Start with the item count. That single check tells you which path you are on and saves you rebuilding actions you do not need to touch.

References

Thank you!
Proud to be a Super User!
🏷️ Need more help?
✅ Don’t forget to Accept as Solution if this guidance worked for you.
❤️Your Like motivates me to keep helping