bedeho
commented
1 year ago oh, what do we do about this?
Closed zeeshanakram3 closed 1 year ago
bedeho
commented
1 year ago oh, what do we do about this?
zeeshanakram3
commented
1 year ago oh, what do we do about this?
There is a quota usage table provided by Youtube which lists what each API operation costs, hopefully, as a first step, by verifying the youtube-synch calculation against the cost of each operation specified in this table we should be able to identify the discrepancy.
zeeshanakram3
commented
1 year ago Addressed in #201
Context
Youtube tracks the API usage in the form of quota points (default max limit is 10,000 per day). Youtube Data API does not provide info about current quota usage So YouTube-synch BE manually tracks quota usage by aggregating the Quota used by each request based on this quota calculation scheme
Problem
There is some discrepancy b/w quota usage calculated by YT-synch & what is being shown Google console dashboard. YT-synch calculates less than what is actually used.
YT-synch exposes the current quota usage/availability in API endpoint, and Atlas uses that to ensure whether creator can be onboarded successfully or not(if quota is not available Atlas asks creator to retry later). Now if all quota has been consumed and YT-synch api says that quota is available(because it under calculated), this could create problem/confusion for creator onboarding