| Known Issue ID | FMEENGINE-99411 |
| Feature | Esri ArcGIS Feature Service Reader (Esri ArcGIS Connector package) |
| Product | FME Form, FME Flow |
| Versions Affected | Esri ArcGIS Connector package 3.25.3 and 3.25.4 |
| Status |
Resolved Esri ArcGIS Connector package 3.26.1 |
Issue
When reading a feature service on ArcGIS Enterprise or a standalone ArcGIS Server, Esri ArcGIS Connector package version 3.25.3 and 3.25.4 can stop at the layer's Max Record Count, commonly 1000 or 2000. The translation succeeds, and the log reports the reduced count as though it were the whole layer:
ArcGISFeatureServiceReader: Reading 2000 features in 2 batches of up to 1000 features
Nothing in the log or output indicates the read was incomplete. Any output written from an affected service with one of these package versions may be missing features.
Feature services on ArcGIS Online are not affected. If a reader connecting to ArcGIS Online stops at 1,000,000 features, see Known Issue: ArcGIS Feature Service Reader Limited to 1,000,000 Records After ArcGIS Online June 2026 Update.
Cause
Before reading data, the reader asks the service for the object IDs of all matching features, then pages through them. Package 3.25.3 added resultRecordCount to that request to work around a limit introduced by an ArcGIS Online update in mid-2026.
Feature services published from registered data on ArcGIS Server and Enterprise 11.3 and earlier answer that request with only Max Record Count object IDs and omit exceededTransferLimit. Without the flag, the reader treated the short list as complete and stopped after one page. Hosted feature layers are served by the ArcGIS Data Store, which returns the full set. Package 3.26.1 reads the full set from both kinds of service.
Resolution
Update the Esri ArcGIS Connector package to version 3.26.1 or newer. The fix is published on FME Hub and installed without an FME upgrade. The package requires FME 2024.0 (build 24187) or newer.
In FME Workbench, go to FME Options > FME Packages, click Check for Updates, select Esri ArcGIS Connector and click Update.
On FME Flow, packages are installed by publishing from FME Form. A workspace published with an affected package version keeps using that version until it is republished. Update the package in FME Workbench first, then republish each workspace that reads an affected service and upload the package when the publishing wizard offers it. See FME Flow Troubleshooting: Packages.
After updating, rerun the workspace that reads an affected service. The log line above should now report the layer's full feature count.
Check whether your service was affected
Whether a service was truncated depends on how it was published and the ArcGIS version.
In our testing, feature services published from registered data, such as an enterprise geodatabase, truncated on ArcGIS Server and Enterprise 10.8.1 through 11.3 and read in full on 11.4 and later. Hosted feature layers read in full on every server we tested, including a server where a referenced service truncated. Hosted layers are stored in the ArcGIS Data Store and listed under the Hosted folder of the server's REST services directory.
Treat 11.3 as an approximate boundary. Run the following tests to check if any service you’re reading was affected.
Open the following two requests in a browser, using your own service URL and layer index. Both requests are read-only and safe to run against a production service.
.../FeatureServer/0/query?where=1=1&returnIdsOnly=true&f=json.../FeatureServer/0/query?where=1=1&returnIdsOnly=true&resultRecordCount=1000000&f=jsonIf the second request returns fewer object IDs than the first, the service is affected. If both requests return the same IDs, the service was never affected.
If your workspace uses the shipped ArcGIS formats in 2026.3
The Esri ArcGIS Portal Feature Service (ARCGISPORTALFEATURES) and Esri ArcGIS Server Feature Service (ARCGISFEATURES) formats that ship with FME 2026.3 truncate in the same way. These formats are deprecated and hidden as of FME 2026.3, and updating the Esri ArcGIS Connector package does not affect them because they are part of the FME installation, not the package.
We strongly recommend migrating to the Esri ArcGIS Feature Service reader from the Esri ArcGIS Connector package to receive up-to-date fixes, like this one. Working with Esri ArcGIS Feature Services in FME has migration steps for each format.
Support
If you cannot update the package, or the reader still stops after updating, please open a support case. Include the package version, the ArcGIS Server version from .../rest/info?f=json, and the results of the two requests above.