G Suite "Download Quota" API Ban

Streaming cache is set to Auto… should it be legacy?

1 Like

Strictly as a test it might be interesting. I know that auto enables the disk based caching an it may be taking too many bites in a short time trying to fill the disk cache. Auto only buffers a small amount but it may be enough to gap the hits on Gdrive enough to avoid the too many hits in a short time ban.

Just remember, this is strictly a SWAG. :wink:


Running into this problem more and more, often just drops the movie half way through and then I can’t access anything until the ban is lifted.

Checked the logs, google seems to see Infuse as “downloading” the file over and over again every 2 - 3 mins on average which for a 3hr 4k movie or 2 basically generates enough traffic to hit google’s supposed 10TB daily limit.

Edit: Some inferences made here, it’s not like google exposes any measurements against their daily quotas but looking at the audit logs, this seems to be the case.


Wow… @james, can this be confirmed as true? If so, is there anyway around this? This would make it essentially useless for playing 4k from google… there’s gotta be some work around.

1 Like

I just got hit by this for the first time. All my Apple TV’s just throw the error. When I play stuff off the google Drive app(iPhone and iPad), they play. Does google differentiate when I use infuse vs their own app to play stuff?

1 Like

Today’s 6.4.6 update adds a lightweight cache for the Google Drive API.

According to our tests this can drop the API usage during indexing by up to 50%.

Let us know how it goes for you. :slight_smile:


Great news! I’ll be on the lookout for the update on the App Store today :slight_smile: praying this helps a lot with the ban issues were all experiencing. :crossed_fingers:

@james you know what else would be super helpful… is to have an option to scan changes to specific folder shares (google in my case) so that it doesn’t check all the check marked shares each time. Possible? That may also help with api request counts…

1 Like

Updated to 6.4.6 a bit ago… will see how it helps avoid the downloads api ban. Others here with the same issue… try it out as well and let’s see if it’s better now and report back to the infuse team :slight_smile:

1 Like

@james what version is iCloud stored artwork/metadata supposed to come to infuse? 6.5.0? Will that also help in lowering API requests from google? Thanks!

1 Like

You can always see what features are currently planned and what release they are targeting here

Just remember, this is not written in stone and can be fluid at times.

1 Like

Thanks! I noticed iCloud artwork sync keeps getting pushed to future releases :frowning: bummer… that’ll be really nice when it’s here.

1 Like

A post was split to a new topic: Unable to select artwork from Google Drive

Since the new update there’s been no bans for me. Thanks looking at this.


Greetings from Brazil,

I’ve read the page Metadata 101 – Firecore and it appears that Infuse works just like Kodi Movie/TV Show scrapper - it would rely on a pre stablished naming convention to be able to get movie/tv show information from different sources - this info can also be found here Infuse Metadata Source.

I am using Infuse to play my content that is sourced from Google Drive. The option " Embedded Metadata" is disabled. I’ve noticed that every time I open inFuse and start navigating thought the list of my movies I can see between one to six download records on GDrive logs for each movie it shows on my screen. I would like to reinforce that I did not play ANY of these files.

Please find a sample below from the logs: inFuse-Download-Problem - Google Sheets

Why this is a problem? I was informed by a GDrive Support Analyst that every single download row found in my log counts as if the file was fully downloaded regardless of whether or not it actually happened. The thing is, a movie can be as big as 40-60 GB and all that data counts against my download quote in Google Drive (which is not really informed). When that download limit is reached, Google would lock me out for 24 hours, which is really bad!

So my questions are I need your help with to answer to resolve the problem:

  1. Why is inFuse doing that?

  2. Wasn’t it supposed to use only filenames/foldernames to crawl and display movie/tv show info?

  3. Is there an option to disable this behavior and avoid it from happen?


1 Like

I moved your post to this thread that should shed some light and hopeful answer your questions. :smiley:

Have you updated to 6.4.6?

1 Like

Thanks for doing that. Reading all of this helps to understand better what is happening, for sure.

To answer your question: yes, it is 6.4.6.

That is a pretty good explanation. While we are facing this problem, is it possible to add an option to not to fetch any data out or the files themselves other than the necessary to scrap the movie/tv show details from the scrapper services (which I assume are only filename and folder names so no file download necessary) to completely avoid any download up to the moment the user actually hits the play button? So the user can choose on get more info about the movie (like codecs etc) at the price of having more data downloading from Google counting against the quota or have less info (not sure if ppl cares anyway, since they already know their content when they upload to Google) and more free download quota.


1 Like

You shouldn’t be seeing any more issues with the 6.4.6 update. When did you update to 6.4.6? It was released on July 7th but didn’t get wide spread distribution until the 8th so you shouldn’t be seeing the problems after the update.

From your logs it only shows up to the 8th so that appears to be before you updated to 6.4.6

Hi @NC_Bullseye:

I have just tested again. Opened inFuse and just navigated through the movies collection without clicking on ANY of them for about 7 minutes or so and it shows 332 downloads records which occur during that time which you can find in this GSheet (inFuse-Download-Problem - Google Sheets).

Please let me know anything else I can do to help solve this problem.

1 Like