Recent AGOL Update restricts the number of records that a AGOL reader can read to 400k

a workaround might be on the reader to reduce Feature Per Request, perhaps half it and see it that helps

a workaround might be on the reader to reduce Feature Per Request, perhaps half it and see it that helps

 

Thanks for the response. I already have this set to this value. The problem seems to be a maximum number of records that I can return overall (not per request). ESRI has recently set a limit to the number of records you can return to 400k records. Previously I could return all the records from the hosted service using the AGOL reader no matter how big hosted service was. 

Looks like Safe put out a workaround using the api...https://support.safe.com/hc/en-us/articles/47037080794381-Known-Issue-ArcGIS-Feature-Service-Reader-Limited-to-100-000-Records-After-ArcGIS-Online-June-2026-Update  

Thanks ​@jasonc this would have driven me crazy.

I was working on a workflow the other day to update the layer definition and change the value, when I went back to it today I saw that all my layers now have a limit of 1 million features, they were at 400k previously.

Hi everyone,

Just wanted to let you know we’re working on updating the ArcGIS Feature Service package so that it can read more than 1 million features.

We’ll let you know when the update is released! 

Update: the ArcGIS Feature Service package has been updated to read all features. It now handles the 'maxIdsCount' property, so it correctly reads past the 1 million feature cap from the June 2026 AGOL update.

Given the disruption this caused to production workflows, I'd recommend migrating to the package integration now rather than waiting. The package is also the best way to get timely updates whenever there are REST API changes, and it will be the integration that receives all new feature updates going forward. See this article for details on migrating from the shipped integration to the packaged one.