Starting today I keep receive 0 users live on website (even when they are online and can be seen in analytics website). First I’ve got some error saying that API has timed out after 5000ms or something. Tried to delete de error but it wasn’t gone, remains on the plugin error section.
Now I’m receiving this:
Număr:116
Cod eroare Ajax: None
Cod eroare API: 429
Motiv eroare API:
Exhausted property tokens for a project per hour. These quota tokens will return in under an hour. To learn more, see https://developers.google.com/analytics/devguides/reporting/data/v1/quotas
Detalii eroare API:
Array
(
[0] => RESOURCE_EXHAUSTED
[1] => trying to refresh token
)
This topic was modified 1 year, 3 months ago by i0n1ca.
Most probably you were sending too many requests in a short period of time. You should clear the error after an hour and retry. If the issue persists you should clear authorization and re-authorize the plugin.
I am not trying anything just having my dashboard open like always during the day. And after some article published I’m refreshing the page. I will clear the error again (but when I do this nothing happens the error remains there). Probably the re-authorize the plugin again will do the magic.
The timeout should be increased to 30 seconds on new version. I’ve also noticed these timeouts lately and 30s seems to be more than enough on my tests.
I’m going to mark this thread as resolved. If there are further issues please post here and mark it back as unresolved.
I’ve never had this issue before, everything was fine till recently. Probably Google did some modifications to their API or so. Today I have again the error with tokens. How can I consume them? I’m just refreshing my dashboard after 1-2-3 articles written and that’s it, nothing special.
Număr:134
Cod eroare Ajax: None
Cod eroare API: 429
Motiv eroare API:
Exhausted property tokens for a project per hour. These quota tokens will return in under an hour. To learn more, see https://developers.google.com/analytics/devguides/reporting/data/v1/quotas
Detalii eroare API:
Array
(
[0] => RESOURCE_EXHAUSTED
[1] => trying to refresh token
)
I use Analytics plugin in wp-admin with the option Real-time to see the number of online users. This was my option from many years now …
This reply was modified 1 year, 3 months ago by i0n1ca.
IMHO considering the behavior described above you may be hitting the Realtime Concurrent Requests Per Property, which is 10.
Please note that a token doesn’t equal a request. Depending on request complexity it can consume more than a token. So if the plugin is trying to make a request for real-time reports and at the same time you force the retrieval by doing consecutive requests it can hit that limit.
Please try not to force refreshes and see how it goes. Also considering the issue you had with Safari, clearing the cache for the domain and disabling browser extensions would be helpful.
I have a few extensions, but now I’m working on a laptop with Windows and Chrome which I have for almost a year since I’m doing the same thing / writing articles and using dashboard with realtime view without any issue till now.
From my side nothing has changed and what I am seeing now probably is not the plugin but Google!
I am very curios if I am the only one with this issue or somebody else have it too. 🙂
After all everything adds up without necessary new limitations. If we’re considering that lately the latency on API requests is high (reason for the PHP cURL timeouts) multiple concomitent requests are very possible on repeated refreshes.
I think some how I’ll found the issue but I don’t know what is causing it.
I am using Chrome / Windows 11 and I have wp-admin (dashboard) open. I don’t refresh it for 10-20 minutes and I am doing other work on other tabs. When I’m coming back to the tab without refresh it the number of live users keeps fluctuating (20-22-18-17-19 …). After refresh of the page the number doesn’t fluctuate keeps normal with the live users.
I think that when fluctuating it sends requests on request and this is why we get timeout or exhausted tokens.
This type of usage I did before and this didn’t happened.
Please check if you can replicate the issue with v6.3.6. While I wasn’t able to replicate it, I found a few issues based on the above details which could have caused problems.
