The following are known issues within Cloud Quotas.
Quota values during rollouts
Google Cloud sometimes increases the default quota values for resources and APIs. These changes take place gradually, which means that during the rollout, the quota value that appears in the Google Cloud console or Cloud Quotas API won't reflect the new, increased quota value until the rollout completes.
If a quota rollout is in progress, an informational message appears at the top of the Cloud Quotas page and the rolling update indicator appears next to the quota values impacted by ongoing rollouts. For details, see View ongoing rollouts.
For troubleshooting steps, see Exceeding quota values during a service rollout.
Quota preference contactEmail field is required
To update the QuotaPreference value through the Cloud Quotas API,
the contactEmail field is required. This email address cannot be a group
email.
For examples of using QuotaPreference in the API, see
Implement common use cases.
Requests for adjustments on quotas that have no usage
If you request an adjustment for a quota that has no previous usage, you won't see that quota available in the Google Cloud console. However, you can still request a quota adjustment through the API.
For example, you might clone a project and know ahead of time that you need to
increase the value for
compute.googleapis.com/local_ssd_total_storage_per_vm_family. Although you
won't see that quota available in the Google Cloud console, you can still
use the API to
request a quota increase.
For more information, see View ongoing rollouts and Request adjustments on quotas that have no usage.