Hello, I am hoping a billing specialist can review one invoice for us.
Our Pro team (pink-cowz-hq, one seat, about $24 a month since August 2026) received two partial invoices in October, both almost entirely one line: Build CPU Minutes. Invoice N3UVBPY5-0008 ($174.04, 21 October) and N3UVBPY5-0009 ($126.95, 22 October). Everything else on them totals under $2.
What happened: the team's build machine was Elastic and On-Demand Concurrent Builds were on "Run All Builds Immediately" on every project, both defaults we never chose. Our team Activity log shows that on 15 October the System automatically moved both projects from 8 CPUs to 30 CPUs "because a previous build took a long time", with no action from us. From then on 468 ordinary pushes in nine days became 76,974 CPU minutes. A $200 Spend Management budget was in place but, with pausing off, it only sent alerts.
What we did: the night we understood it, Basic machines on all 12 projects, concurrent builds disabled, Ignored Build Step so each project builds only its production branch, budget lowered to $50. Both invoices are paid.
The in-chat refund form approved the first invoice (N3UVBPY5-0008, $173.10, thank you). For the second (N3UVBPY5-0009) the same form returned "Automatic Refund Limit Reached" for its $105.63 of Build CPU Minutes, and the assistant said it could not open a case.
Could someone at Vercel review a one-time credit for N3UVBPY5-0009? We are a small UK start-up with one developer and this was our first overage. Screenshots of both invoices, the Activity log entries (the System's 30-CPU escalation and our fixes) and the Spend Management panel are attached. Thank you.
Joseph Talbot, Pink Cowz Ltd