Stale "credit usage exceeded" flag blocking production deploys despite available credit balance — jarvis-lab-capturas

Admin
1

Team: cristianbernal654’s team

Site: jarvis-lab-capturas (site ID: f560c7ac-43fd-418e-9057-000277a67097)

Plan: Free (300 credits/month, billing period Jul 5-Aug 4, 2026)

I’m seeing an inconsistency on the Usage & billing page:

  • The “Credit usage breakdown” widget shows 302.5 total credits consumed this period (300 from 20 production deploys, plus 2.5 from web requests/compute/bandwidth), which is 2.5 credits over the 300/month Free plan allowance.
    • The team-level banner states: “cristianbernal654’s team has run out of credits. Your projects may go offline and production deploys and Agent Runners are currently disabled.”
      • However, the separate “Credit balance” widget on the same page shows 29.9 / 30 credits remaining, granted July 14, 2026, expiring August 4, 2026 - a distinct credit grant that appears almost entirely unused.
    • Despite this apparently available balance, production deploys remain blocked. Concretely: we merged a hotfix PR into main for jarvis-lab-capturas at commit 8a7d27e15fa0a39088e0b703b445018a2b3fa63f. The corresponding production deploy shows as “Skipped - Skipped due to account credit usage exceeded” (today), even though Deploy Preview builds on the same commit range completed normally.
  • This hotfix resolves a P0 authentication bug in production (GET /api/status returning 500 instead of 401 for unauthenticated requests, due to a MissingBlobsEnvironmentError). The fix is fully tested and verified on the Deploy Preview, but we cannot get it to production because the production deploy is being skipped.

Could you please check whether the 29.9/30 credit balance should be applying to unblock production deploys, and clear the “credit usage exceeded” flag if this is a stale/incorrect state? I’d prefer not to upgrade the plan or purchase additional credits if this turns out to be a display/sync issue rather than a genuine plan limit.

I see several other recent reports of the same behavior on this forum, so this does not appear to be isolated to this account.

Happy to provide any additional account/site details needed.