Hi @nsher ! Also apologies for the delayed reply, we had to turn on verbose logging to be able to get an example request ID for a call where we experienced a delay in license info becoming available.
Here’s the request ID: 54a58812-829e-40ca-a4f9-18370a3c5240
We identified it as a problematic request because the response was missing the license object altogether, unlike a typical response.
Other possibly relevant info is that this request was made by one of our Confluence Cloud apps, and the request time is 1698943278701 (Nov 2).
I hesitate to post the entire response since there is some customer info there (from the host object), but let me know if I need to provide more information.
As an aside, I would argue that even a delay of “a few minutes” is really quite large and highly detrimental to our analytics tracking. We cannot have the app hang while the info becomes available, and we are having to implement a resource-expensive retry method that runs in the background and continuously polls the API until we get a full response. I am not sure how to elevate this issue but I would highly encourage Atlassian to work on this!
(or, just include all the license info such as license status, license type, etc. in the /installed lifecycle callback like they started doing with entitlement_number recently, seen here: Licensing fields now available in Connect lifecycle event)