Select to view content in your preferred language

Unable to Query Public Layer

375
5
04-04-2025 09:57 AM
Labels (1)
jvarasanz
Regular Contributor

Good morning.

I have a hosted feature layer and a corresponding view that I intend to share with the public. However, when shared publicly, neither the layer nor the view displays pop-ups, nor can they be queried through the REST endpoint.

Error below (only if shared to the Public):

API calls quota exceeded (7550 request units)! maximum allowed request units (6000) per Minute. Retry after 60 sec.

Could you please advise on how to resolve this issue?

Javier

0 Kudos
5 Replies
thesweenis
New Contributor

Can you share the URL for the HFL and the HFLV you can share?  I'd review it and let you know what I see.

 

0 Kudos
jvarasanz
Regular Contributor
0 Kudos
ChristopherCounsell
MVP Frequent Contributor

Your org is exceeding its usage threshold. I've explained this already here:

https://community.esri.com/t5/arcgis-survey123-questions/pulldata-layer-function-not-working-for-pub...

You should be reviewing your organisation and workflows or contacting tech support.

0 Kudos
jvarasanz
Regular Contributor

Thanks Christopher,

We are still confused how a query is successful when I don't share publicly, but not when it is shared, which is when it is consistently failing. Additionally, I am testing in Survey123 Connect by pulling the json string from the layer once I hit the map. Why would that create a spike?

Any other automated processes or tasks are successfully running.

I hope this helps. Just in case we are at 11% of our storage capacity. 

Thanks again.

0 Kudos
ChristopherCounsell
MVP Frequent Contributor

Can you share the xlsform?

Storage capacity is not relevant. 

If you go to the layer item details > usage, is the a large amount of usage (requests) on the item? Does it spike when you share publicly?

What I am saying is that that error message is indicating the number of requests made to your org is exceeding the threshold. Why this is happening is yet to be identified, but that's the response from the server. It could be that something is hammering your publicly accessible layer. Or coincidence. Or the pulldata expression itself, but that's not normal.

0 Kudos