Reduce the amount of license checking in order to make Pro more responsive - EDITED

[RTPL_AU]

2024-1-13: In Product Plan  - ENH-000172764

EDIT:
Following the AGOL outage last week and Esri rebooting a few things, this behaviour seems to be much less of an issue.  If you still experience it please add your kudos but also a context comment so the Esri staff have a bit more information to go by to prevent it from happening again.

EDIT 2:
Nope. Must've been a temporary reprieve as it is back to do at least 4 checks when you paste a value into an attribute table; amongst other things.

Pro 3.3.2 seems to do a LOT of license checking.

When you open the Diagnostic Monitor you will see that for almost everything you do, Pro will do multiple successive license checks. 

Paste a value into an attribute table of a locally saved FC in a local FGDB: 4 checks

Rename a map: 76 checks

The log will be filled with:
<HTTPRequest start="5/11/2024 10:20:05 AM" duration="235" thread="39940" status ="200" url="https://www.arcgis.com/sharing/rest/portals/MYAGOLACC/subscriptionInfo?token=THETOKEN&f=json"</HTTPRequest>

I understand the need to monetise and audit users but how about doing this during an idle moment/startup and reporting a timestamp so you do it once a day?

Rename a map:

+ (had to scroll to copy them all)

That is 19 seconds of unresponsive UI.

[KoryKramer]

As @RTPL_AU noted, we think we have identified the issue and are looking into a way to cache the info needed and only re-cache when necessary (like if you change your active portal during a session). 

[RTPL_AU]

@KoryKramer 

Edit: Joke deleted

I have not seen this issue raise its head recently and you had the AGOL issue 2 weeks ago. 

Could it be that the problem causing this idea is server side and not client side?

Mitigating problems caused by server-side failures by local caching of authorisations per session would still be a great outcome in case of unexpected AGOL AGI walkabouts...

[RTPL_AU]

Hi @KoryKramer 
Has this been fixed server-side or did it go away by itself?
I have not seen this behaviour for a while now.

If you fixed it - thank you.

If you didn't fix it - good luck on the hunt.  😀

[RTPL_AU]

Fixed in 3.5; making 3.4.x even less appealing.

[RTPL_AU]

@KoryKramer  I just noticed that this is behaving a bit strangely.
When you are signed in to another portal - and set that as the default portal for publishing, although it is not the licensing portal, Pro will do license checks against that portal? This doesn't seem to be affected by checking out a license as you obviously can't check out a publishing session - if that makes sense?

To prevent any misconceptions and assumptions at my end, can you please explain what is happening with these checks and the reasoning behind it?

This is just such a bizarre thing to have happen and I cannot fathom how intrusive it could be if you have a slow or high-latency internet connection. 

Second to this - Does Esri do stuff at night (USA time) that could influence this behaviour? It seems to be worse in our afternoons - your nights.

[KoryKramer]

Hi @RTPL_AU I saw in another post that you mentioned you don't see these excessive calls being made in ArcGIS Pro 3.5. I wanted to acknowledge that we did install a code change to address what you reported here. Given the information we had, we feel that the change should address what was reported.

Cheers,

Kory

[RTPL_AU]

@KoryKramer  This has made a tangible difference in some workflows. Thank you.