Every deploy that builds your code uses build minutes from a monthly allowance set by your plan. The plan also decides how many builds run at the same time and how long one build may take.
See how many minutes you have left
Open the Subscription page and look at Build minutes left. It shows the minutes left out of the month's allowance, with the minutes used so far underneath. An unlimited allowance shows "∞".
The allowance is per UTC calendar month and starts again on the 1st.
What counts
A build is timed from the moment it starts until it finishes, and the month's total is rounded up to whole minutes. The minutes count against the month the build started in.
- Failed, cancelled and timed-out builds count for the time they ran.
- Waiting in the queue does not count.
- A rollback reuses an earlier build, so it uses no minutes.
- Deleting a project does not give back the minutes its builds used.
When the minutes run out
Once the month's minutes are used up, new deploys are refused with "Your organization has used all its build minutes for now. Upgrade your plan to deploy before they reset." Apps that are already running are not affected. Deploys work again on the 1st (UTC), or straight after you upgrade.
When usage passes 80% of the allowance, starting a deploy also sends a "[HCode] Build Usage Warning" email to the person who started it, with the minutes used and remaining.
Temporary extra minutes
Support can add extra minutes for a set period, for example during a launch. The card then has a line starting "Includes" with the extra minutes and the date they end. After that date the allowance goes back to the plan's number. Ask at [email protected].
Builds that run at the same time
Your plan sets how many of the organisation's deploys can build at once. A deploy started while that many are already queued or running is accepted and waits its turn. The dashboard shows a message such as "Queued — starts when your running build finishes." Waiting deploys start in the order they were queued, and a waiting deploy doesn't block stopping, starting or restarting the project.
The longest a build can run
Each plan caps how long one build may run, and no plan allows more than 120 minutes. A build that hits the cap is stopped and the deploy fails with "build exceeded max duration of" followed by the cap. The minutes it ran still count. The warning email lists your plan's cap as "Max build duration per deploy".