This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(304, 76%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKM%3C/text%3E%3C/svg%3E)
We were doing an ExportDatabase operation on our production database. This is part of our release pipeline, to do a backup before deploying new code.
The github action timed out eventually since the export job got stuck at 1% and was stuck for 8 hours. We then used az cli to cancel this job. This job is now stuck at status CancelInProgress. It has been so for 22 hours now.
We cannot do any more backups. We cannot cancel the job more than it being cancel in progress. We cannot deploy our new code the client is waiting for.
Is there any way to fix this "hostage situation" other than paying for a support plan to ask Microsoft themselves a "technical question" with their broken system?
A server restart could perhaps fix it we thought, however disruptive that is for the client. But there is no way to restart an SQL server in Azure from what we could gather in the documentation.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 4%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPC%3C/text%3E%3C/svg%3E)
Hi Kalle Macklin,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
As per your issue, I could understand that the export operation for the azure sql database got stuck at 1% since 8 hours and you tried to cancel the operation, which got stuck at cancelling in progress state from 22 hours.
I request you to please confirm, whether you followed the below steps to cancel the operation.
How to cancel Azure SQL Database Import or Export operation | Microsoft Community Hub
Kindly follow the below steps and share the screenshot of the export/import history page of the database and also share the request id of the operation which got stuck and share the size of the database.
I hope this information helps. Please do let us know if you have any further queries.
Are you a Microsoft employee?
Are you a Microsoft employee? It says "Microsoft Vendor" under your name, but I'm new to this QA site so I'm not sure who's who and I can't fully disclose potentially sensitive information such as database name
This is a public site, so don't disclose anything sensitive here!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 60%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
Hi Kalle Macklin,
Is that Backup still in Hung state?
The solution is to pay for a support plan since that is the only way you are allowed to contact Microsoft about this bug/error, due to it being a "technical question".
Yes and no. I got a briefing about the Priority Support through Q&A, and I understood it, support engineers can contact you through private messages to resolve such issues. (I am not a support engineer, just a community member.)
On the other hand, you said "production" database, and for a production database, I think you need a better support contract than "Developer".
Hi Kalle Macklin, the private message option is only accessible to Microsoft support engineers. can we please work on this thread offline? Please send us an email on azcommunity [at] microsoft [dot] com with Sub - "ATTN: PratikLad" and following details in the email body:
The solution is to pay for a support plan since that is the only way you are allowed to contact Microsoft about this bug/error, due to it being a "technical question".
I have marked an answer, please don't contact me anymore regarding this.
PraktikLad above has already private messaged me, refusing to explain who they are, trying to get tons of sensitive technical details from me so right now this is only a breeding ground for scam attempts sadly.
Solution finally:
After either 3 or 4 full days, the job released from CancelInProgress to Cancelled, so perhaps time heals all wounds.