Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Use Markdown for this comment
Set severity, which reflects how much the issue affects the use of the product
Assign issue to yourself
Pending code changes (auto-populated)
[ID: 151537]
[ID: 81767]
[ID: 81766]
Set the version(s) of the product affected by this issue (comma-separated list)
Set the version(s) of the product in which the issue should be fixed (comma-separated list)
Set the version(s) of the product in which the issue fix was verified (comma-separated list)
Set if this issue occurs in production
Set Reporter
Set Type
Set priority, which reflects how soon the issue should be fixed
Set Status
Set Assignee
Set Verifier
Remove item
View or edit staffing
View issue level access limits(Press Alt + Right arrow for more information)
Description
#1Summary: Currently, if a developer has exhausted any of their quota token buckets, further Data API requests will fail with a 429 error. Thus, developers cannot get back the `PropertyQuota`. It becomes difficult for developers to understand the property's current quota status and which bucket(s) have been exhausted at this point. Especially, if other applications have exhausted a quota token bucket, there will not no information from the developer's point of view on the quota tokens.
Provide a way for developers toget back `PropertyQuota` object even if a property has exhausted one or multiple of their quota token buckets. This can be via the Admin API or a Data API method with a separate token bucket.