Select to view content in your preferred language

API Error Open Data Download

16200
46
Jump to solution
06-09-2021 11:01 AM
Tony_J_Van_Der_Wielen
New Contributor III

We started seeing and API error in the download section of our Open Data page. It looks like there are no reported issues on Esri's end https://status.arcgis.com/.

apierror.jpg

Has anyone seen this? Or do you know how to fix it? This is happening with all our content.

Thank you!

Tony

 

Tags (1)
46 Replies
SimonAllard2
New Contributor III

Seems to be working fine Paul! Our site has been acting up quite a bit of late. Sometime it works and sometimes we get the API error. It is very inconsistent. 

0 Kudos
JessicaGormont
New Contributor II

I have just discovered that one of my layers is having this issue as well: https://od-jcwvgis.opendata.arcgis.com/datasets/8d4df0b309944ccf8b72bf0d279a168b_1/explore?location=...

None of my other layers seem to have this issue. I tried republishing the layer and that didn't fix the problem. Our layer is using the ESRI extent, so it's not a projection issue.

Any suggestions?

0 Kudos
MattJinman
New Contributor II

We are encountering the same issue. This was our biggest release of the year - it worked fine yesterday when I previewed the data. Now on release day I get API errors on all forms of data CSV, GeoJSON, Shapefile and KML.

https://geoportal.statistics.gov.uk/datasets/ons::output-areas-december-2021-boundaries-full-clipped...

I've raised a ticket with My Esri and see what they say?

MozaAlhemaidi
New Contributor II

Also, i have this issue with one of my shared layer in the Hub site.

0 Kudos
MichaelJenkins
Occasional Contributor III

We've just started to have this issue too.  With a single layer in a map service that hosts multiple map layers.  All other map layers from this service can be downloaded.  https://gis-kingcounty.opendata.arcgis.com/datasets/kingcounty::zipcodes-for-king-county-and-surroun...

GISP
N8-CORR
New Contributor III

My Hub site starting having this issue out of nowhere last week. Random layers display the error intermittently.

I saw this article posted by Esri: https://support.esri.com/en-us/knowledge-base/error-api-error-next-to-download-options-in-arcgis-hub... but our layers are not shared via distributed collaboration.

I also tried enabling local projects on the site but no dice. Are there any other causes to this issue @ThomasHervey1?

KC
by
Occasional Contributor

Also seeing the "API Error" on some of our datasets on our Open Data site, but not all of them, even though owners haven't been changed, these datasets are different sublayers out of the same ArcGIS Server services, etc.  Developer Tools shows that for the erroring datasets, where the request is https://opendata.arcgis.com/api/v3/datasets/whateverhubidthisis/downloads?parameters=1234 the response is errors: message: "Not Found".  (The previously mentioned https://od-jcwvgis.opendata.arcgis.com/datasets/8d4df0b309944ccf8b72bf0d279a168b_1/explore?location=... I see also has "Not Found" in Dev Tools for its download endpoint)

Taking a look at https://opendata.arcgis.com/api/v3/datasets, seems like that's where all Open Data datasets are, and at the very bottom it has a "last" page of https://opendata.arcgis.com/api/v3/datasets?page%5Bnumber%5D=1420043&page%5Bsize%5D=10 but going to that last page gets you a:

{"errors":[{"title":"Server Error","status":500,"message":"search_phase_execution_exception: [illegal_argument_exception] Reason: Result window is too large, from + size must be less than or equal to: [10000] but was [14200430]. See the scroll api for a more efficient way to request large data sets. This limit can be set by changing the [index.max_result_window] index level setting."}],"meta":{}}

With this in mind, I tried searching for my erroring datasets in https://hub.arcgis.com and as you can guess, they're not showing up; my download-OK datasets show up, but not the API error ones.

Esri:  I think you can try increasing your [index.max_result_window] index level setting for the Open Data/ArcGIS Hub site to see if this fixes the API Errors that we're seeing?  Worth a shot.

Thank you!

0 Kudos