Hi @Khikmatullaev,
I’m sorry you’ve been blocked for this long, especially over such a small past-due amount.
Please send me a private DM with your Databricks account ID, affected workspace ID(s), invoice number (if you have it), and the open billing/support case numbers. Please do not post any of that publicly here.
I’ll help route this internally for urgent review so the team can look into two things in parallel:
- Getting you a working payment path for the outstanding invoice, and
- Reviewing restoration of compute access once billing can validate the account state.
In the meantime, it may also be worth checking whether your account is billed through AWS, Azure, or GCP Marketplace rather than directly through Databricks, since that could change the payment path. If you are a direct customer and can access your Databricks account console billing settings, it may also be worth checking whether you can update the payment method there.
Thank you for spelling out the impact clearly, and I’m sorry again that this has affected your production timeline.
Look forward to your message.
If this answer resolves your question, could you mark it as “Accept as Solution”? That helps other users quickly find the correct fix.
Regards,
Ashwin | Delivery Solution Architect @ Databricks
Helping you build and scale the Data Intelligence Platform.
***Opinions are my own***