Quota Error: too many concurrent connections

  • Resolved gxt

    (@gxt)


    10 years ago

    I keep getting this error:

    Google Post Pageviews Error: Quota Error: profileId ga:1234567890 has too many concurrent connections.

    and that’s coming from the Google API, and it’s how it should be.

    But if the content that was requested before is cached why when the plugin disconnects everything goes to zero even the cached content?
    Wouldn’t it be better when the API gives an error, cached pages still display the number that was cached and not going to ZERO?

    I don’t know how it is structured and how it works, but, for me if page views for a page are fetched once and cached.. the plugin should display that numbers till the next time. Also the cache must be flushed depending on the time when the record was cached, not everything at once;

    e.g. (if the cache is set to 1 day)
    – page1 was cached 1 day ago
    – page2 was cached 2 mins ago

    page1 must be fetched and cached again.
    page2, that was cached 2 mins ago, stays the same till the next day.

    https://www.ads-software.com/plugins/google-analytics-post-pageviews/

Viewing 1 replies (of 1 total)
  • Plugin Author maximevalette

    (@maximevalette)

    Hi gxt,

    Thanks for the feedback. I didn’t think of this in that way, so to avoid unnecessary requests I returned 0 every time Google was disconnected.

    In the latest version available, if there’s a number in cache it will be returned no matter what.

Viewing 1 replies (of 1 total)
  • The topic ‘Quota Error: too many concurrent connections’ is closed to new replies.