Hi @uhuru_furuta,

Thanks for sharing the exact error — that makes the issue much clearer. The error:

"Serverless warehouse cannot start since workspace 7474651022159303 is no longer eligible for Serverless Compute"

This is NOT just a budget issue anymore. Extending the budget alone won't fix this. Here's what's likely happening and how to resolve it:

Root Cause

When a workspace exceeds its budget and gets suspended, Databricks can internally mark that workspace as ineligible for Serverless Compute at the platform level — this is a backend eligibility flag that is not automatically reset when the budget is extended. It requires manual intervention.

Steps to Resolve

Step 1 — Account Admin Action (Try this first)

• Log in as an Account Admin (not just Workspace Admin) at accounts.azuredatabricks.net or accounts.databricks.com depending on your cloud
• Go to Workspaces → your workspace → Feature Enablement
• Check if Serverless Compute is still toggled ON
• If it's OFF or greyed out, toggling it back ON may restore eligibility

Step 2 — Check if Serverless is disabled at the Account level

• Under Account Console → Settings → Feature Enablement, confirm Serverless is enabled globally for your account
• A budget breach sometimes triggers an account-level disable, not just workspace-level

Step 3 — Contact Databricks Support (Most likely required) Since the error is an internal eligibility flag, this almost certainly needs Databricks Support to flip a backend flag for your workspace. When contacting them, provide:

Ask them specifically to: "Re-enable Serverless Compute eligibility for workspace 7474651022159303 which was suspended due to budget exhaustion."

Important Note

If you are on a Databricks trial (DBU trial or free tier), budget exhaustion can permanently revoke Serverless eligibility for that workspace and it may not be restorable — you may need a new workspace with a paid plan attached.