Youtube Data connector

[gagan_chhabra]

I have been using Qlik Youtube data connector for a while now. For previous 2-3 days, it started giving error that limit exceeded. Exact error message is:

There was an error running the table (Failed on attempt 1 to GET. (The remote server returned an error: (403) Forbidden.){ "error": { "code": 403, "message": "The request cannot be completed because you have exceeded your quota., "errors": [ { "message": "The request cannot be completed because you have exceeded your quota.", "domain": "youtube.quota", "reason": "quotaExceeded" } ] } } )

Looks like the API limit has been reached, but it is not resetting on its own and giving this error for last 2 weeks now.

Can anyone tell me how to reset the API limit for youtube data connector?

[stevedark]

 Which connector are you using, is it via a QWC web portal (on 5555) or the connector that is native in Sense?

It was the case back along that all calls from Qlik, regardless of user, impacted on the quota. I'm not sure if this is still the case, but if so it may be nothing to do with what you are doing, rather than general usage of the connector is up.

Hopefully someone from Qlik will be able to shed more light.

[gagan_chhabra]

Hi Steve,

Yes it is QWC running at port 5555. It was running fine till 2 weeks back. Even if the quota exeeded , it would reset midnight pacific pacific time.

But now it is not resetting on its own.

[stevedark]

I'm not sure what would have changed then.

Do you have a solid incremental load with QVDs in place, so fewer calls to the API can be made?

Steve

[gagan_chhabra]

Hi Steve,

Even if limit is exceeded it should reset after the day. But its not. The issue here is not how to restrict to fewer API calls ,I guess.

[NickBaker]

Hi - there is a known issue with the YouTube Data connector - somehow the API quota limits were reset and we've not had any response from Google on the matter so far. We are actively working on a potential workaround for this but it will take some time to implement unfortunately.

Apologies for the inconvenience.

If you and any other users are still affected by this issue it would help to reply with a 'me too' or +1... that way we might be able to escalate it further.

[Michiel]

Hi Nick,

We're having the exact same issue at the moment. Are there any developments so far? Is there a forum / page where we can see the latest updates regarding this matter? 

Thanks, Michiel 

[NickBaker]

Hi Michiel,

We have identified the root cause: our YouTube GCP project required an audit for continued access but unfortunately the emails about this went to an unchecked email account (still not sure why this happened) resulting in the quota being reduced then revoked. We have submitted the audit form and have a contact at Google who is escalating the issue for us which will hopefully speed up what is usually a fairly protracted process. Hopefully once the audit is complete the quota limits will be reset immediately and the connector should start working again.

Again, apologies for the inconvenience, appreciate this is very frustrating. We'll post on this thread when we get any relevant updates.

[chrisbrain]

Unfortunately we were not successful and Google have not restored this connector's access.

We are now considering whether to reduce the functionality and try again to get it passed through YouTube's audit process.

If you are reading this and have been using the connector it would be useful if you could contact us (DM me or @NickBaker if you like) and let us know the use case and data you were running and we can then see if that is something feasible for us to consider in a future iteration of the connector.

[gagan_chhabra]

Hi Nick,

Is there any ETA to resolution of this issue? As we are already paying large sums for licenses of these connectors.