PULLDATA(@LAYER...) FUNCTION NOT WORKING FOR PUBLIC LAYER

Question

Good morning.

Our survey has suddenly stopped retrieving JSON data when adding a geopoint.

Here’s the pulldata function we are using:

pulldata("@layer", "getRecordAt", "https://services5.arcgis.com/ELI1iJkCzTIagHkp/arcgis/rest/services/MFR_Grant_Eligible_Area/FeatureServer/0",${ProjectLocation})

Please advise, since it's been working fine for the last couple of days. I've tried updating the xlxs form, but it doesn't work in Connect either. I've also tried overwriting the feature service, but still the same result.

Kind regards,

Javier

jvarasanz_nifc · Answer

Thanks Christopher.

It turns out that everything works as long as the layer is not shared to the Public.

Thoughts?

ChristopherCounsell · Answer

Your ArcGIS Online organization has a limit on how many requests can be made to it within a minute. A request may incur 0 to 3 request units, depending on a few factors, but primarily if it reaches the database. Cached requests, no geometry, non-editable requests are all lighter.

When you reach this limit across all services in your org, a 60 second timeout to all services in your organization is introduced.

It's unlikely that a survey pulldata function is maxing out this threshold. Do you have calculate=always? Can you share the XLSForm? Are you seeing this issue when the survey is not in use?

It's more likely that another workflow is causing a lot of requests e.g.:

* You are using scripts or automated tools to make a lot of requests to your organization feature services
* You have a public, viral application
* You have a lot of users
* Anti-practices are present in your environment that may combine with the above

Now testing your survey should be easy - if your org is health when the survey is not available or in use, then it's the survey. Otherwise I'd recommend taking a read of this article:

https://www.esri.com/arcgis-blog/products/arcgis-online/data-management/tracking-your-premium-feature-data-store-key-health-indicators

And you may need to investigate your layers by usage count, content, workflows, etc. If you can't resolve the issue you'll need to consider a premium data store to increase your limit.

jvarasanz_nifc · Answer

I've investigated in more detail and obtained the following errror:

{
"error": {
"code": 429,
"message": "Unable to perform query. Too many requests.",
"details": [
"API calls quota exceeded (6331 request units)! maximum allowed request units (6000) per Minute. Retry after 60 sec."
]
}
}