nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to handle 219000 errors in portal for proxy layers that point to AGOL?

KirkKuykendall1

Hi -

I'm working at a site that's getting a lot of SEVERE 219000 errors in their portal log.

The URLs mentioned in these errors pertain to proxy services controlled by a 3rd party in AGOL.

Is there a way to determine if these errors are a result of exceeding some sort of RU limit, similar to what @MarianneFarretta described here ?

Would it be possible to determine if that 3rd party could reduce these errors our users experience by upgrading their service to a higher Premium Data Store level ?

In situations where no features are returned as a result of exceeding RU limit, is there a map widget available that would allow us to have an experience app present a message saying:

"Data Vendor x RU limit has been exceeded, so no features appear in layer z" ?

Any feedback on this is greatly appreciated!

Thanks, Kirk

Find more posts tagged with

Sharing and collaboration

Accepted answers

All comments

There are no accepted answers yet

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.