Interesting — if other item IDs from the same list work, but anything > 199 returns 404, that strongly suggests the issue is not the module itself, but what SharePoint thinks that ID refers to in your request.
A few common causes to check:
1) Confirm you’re using the list item’s built-in numeric ID column (not a custom “ID” field)
In SharePoint, the real item ID is the system column named ID (Number).
If you’re copying a value from another column (e.g., “ItemID”, “Order ID”, “Title”, etc.), it can look like an ID but won’t work in the API.
Quick validation: in Make, use Get an item with an ID that works (e.g., 150) and look at the output. You should see something like ID: 150. That “ID” field is the one you must pass to Update.
2) Make sure you are not hitting a different list view / different list / different site
If you have multiple lists with similar names or multiple sites, you can accidentally be updating a different list where only IDs up to ~199 exist.
Quick validation: add a Get items (Top = 1, Order by = ID desc) using the same Site + List you update.
If the highest returned ID is ~199, you’re likely pointing at the wrong list/site.
If it returns IDs > 199, then the list truly has them accessible.
3) Permissions can appear “ID-range specific” if those newer items inherit unique permissions
It’s possible older items are readable by your connection user but newer ones have broken inheritance / unique permissions.
Quick validation: try Get an item for one failing ID (e.g., 205). If Get also returns 404, it’s either wrong list/site or permissions.
If you can share 2 screenshots (no sensitive data):
The SharePoint list settings showing the system ID column exists
A Make run output of Get items ordered by ID desc (Top=1)
…I can tell immediately whether it’s a list/site mismatch, a wrong field being used, or a permissions boundary.
When i first encountered this problem i DID try to use the GET ITEM module - and this is when i discovered i couldn’t get any items over 200.
I am also a Power Automate user and normally i would think this is a filter or polling issue - but there are only 328 items in this list, so CRAZY to think it would be an isue.
Always difficult when you come to a new app and get stuck on something that FEELS like it should be easy!
Thanks — this confirms it very clearly now. You’re not on the wrong path at all.
The fact that:
Get item works for a low ID like 5
but fails consistently for IDs > ~199
while the SharePoint UI clearly shows items up to 327+
means the issue is not Make, not paging, and not the Update module.
At this point there are only two realistic explanations, and one is far more common than the other.
Most likely cause: Site/List mismatch (same name, different list instance)
Your Make module is pointing to a different SharePoint list instance than the one you’re viewing in the UI, even though the list looks the same.
This happens very often in SharePoint because:
The same list name can exist in different subsites
A list may have been deleted and recreated (same display name, new internal ID)
A different site collection path is being used
In that situation:
The API-visible list genuinely only has items up to ~199
IDs above that do not exist for that list, so SharePoint correctly returns 404
Lower IDs (like 5) still work, which matches exactly what you’re seeing
Quick 1-minute confirmation (this will make it 100% certain)
Using the exact same Site ID and List ID shown in your Make run, add a Get items module with:
Top:1
Order by:ID desc
Then check the returned item’s ID.
If the highest ID returned is around 199 → confirmed: you’re pointing at a different list instance than the one shown in the UI screenshot.
If it returns 300+, but Get item(327) still fails → then it’s a permissions / unique permissions issue on newer items.
Typical fix
Re-select both Site and List using the picker (not hard-coded IDs copied from URLs), and make sure the selected site/subsite exactly matches where the list actually lives.
You’re absolutely right that this feels like something that should be easy — Power Automate users hit this exact same trap. SharePoint’s UI and API references don’t always line up intuitively.
Added the Get List MODULE, selected the LIST from the drop down and increased the records to 1000. Received 108 records of the 164.
So this confirmed i am pointing at a different list instance - i used the PICKER and still having same issue.
This is kind of funny - compared to Power Automate this feels like such an easy scenario i have built, but been so difficult! The joys of learning a new interface i guess.
What is your goal?
What is the problem?
What have you tried so far?
Create public scenario page
Screenshots: scenario setup, module configuration, errors
