Build fails when Netlify’s @netlify/database extension calls createSiteDatabase, which returns:
status: 403
message: ‘database feature not available for this account’
This aborts the build (exit code 4) before any migration runs. The error indicates the account is being read as free-tier, which does not include Netlify Database.
However, my Team Billing page confirms:
• Pro plan is active, effective July 14, 2026
• 20,000 Pro plan credits granted July 14, 2026 (13,502.7 remaining)
• A separate grant of 1,500 credits dated July 13, 2026, with no expiration
The existence of two separate credit grants one day apart suggests the account briefly changed tiers around July 13 before Pro took effect July 14. My working theory is that a free-tier downgrade flag was set during that window and never cleared when the account moved to Pro — so createSiteDatabase is still checking against stale entitlement data even though billing is correctly showing Pro.
This matches the timeline exactly: the database was working fine (the call is idempotent and was returning the already-provisioned database) until it was deleted during a branch cleanup, and now that a new database needs to be created, the stale downgrade flag is blocking it.
Could you please check the entitlement/feature-flag record for this account and manually clear the free-tier flag so it reflects the current Pro plan? Happy to provide the site ID, team ID, or any further logs needed.
Quick scope update on this ticket to help with triage:
- Root cause remains the same as previously reported: no database is provisioned (deleted during branch cleanup), and attempts to recreate it fail with 403 ‘database feature not available for this account’ despite an active Pro plan
I wanted to flag this because our conversions are actively picking up right now, so every hour this stays broken means real customers hitting save and getting an error at exactly the wrong moment — actively costing us conversions. I’d appreciate this being prioritized accordingly.
Still happy to provide site ID, team ID, or logs to help resolve this quickly.