How to resolve failed deployments when quota limit errors indicate exceeded maximum builds

Issue

• Deployments are currently timing out for some of our services, causing the deployments of those builds to fail. When looking at the console for the CI, I see the following error:
  

  {"status":403,"message":"Exceeded Quota Limit","errors":[{"reason":"exceededPlanMaximum","context":{"message":"The provided plan [projectname] allows for a maximum of 250 builds","param":"build","attemptUsage":251,"quotaMax":250}}]}

Environment

• Liferay Cloud

Resolution

• This error being seen is expected behavior, and will only be encountered in projects where a high number of builds are submitted in short succession (in the example error above, 251 builds were attempted within 24 hours). Further builds will be prevented from being completed for a time until the plan's quota timer resets.

Additional Information

• Builds listed on Deploying Your New Build via the Liferay Cloud Console consolidate all services under one Build ID, however the API for this quota treats each individual service within a Build ID as a separate build (resulting in more "builds" from the API perspective).
• Whenever the number of new builds created in a 24-hour period exceeds the maximum number of builds allowed by a project plan's daily limit, this error will be encountered. As such, limiting the number of builds submitted in a day will prevent deployments from failing due to the quota.
• This quota automatically resets daily, and new builds can be submitted again as soon as the reset has occurred.
• If this becomes a recurring issue for your team and you'd like to have the quota increased, you can open a Help Center ticket to make this request.
• More information on the Liferay Cloud Deployment Workflow can be found in this overview article.