Mysql Flexible Server is Stuck updating and I can't stop or start it.

Hi there nick marino

Sometimes Flexible Servers get stuck during scaling or maintenance. First, check the Activity Log and portal notifications—updates can take a while. You can try forcing a restart via CLI:

az mysql flexible-server restart --name <server-name> --resource-group <rg-name>

If it stays stuck for more than ~2 hours, open a support ticket—Azure can manually unlock the server safely. Avoid making other changes until it clears.

If this helps kindly accept the answer thanks much

When i try that command I get this

myserver is busy with other operations in 'Stopped' state.

Code: OperationNotAllowedForNonSucceededServer

How can I open a support ticket? I don't see the optioin anywhere

Hi nick marino,

Thanks for reaching out to Microsoft QA! If your Azure Database for PostgreSQL Flexible Server is stuck, here are some troubleshooting steps you can try.

Error usually means there’s a long‑running backend operation still in progress (or the server isn’t fully in a Succeeded/ready state), so the CLI blocks actions like restart.

Here’s a clean, practical way to work through it:

What the message means

myserver is busy with other operations in 'Stopped' state: The server is currently Stopped, and Azure still has an operation queued or running against it (update, start/stop, scale, patch, etc.).

OperationNotAllowedForNonSucceededServer: The server’s provisioningState (or the visible state) isn’t Succeeded/Ready. Azure disallows management operations until that state clears.

Quick checks & recover steps

1. Confirm exact state and provisioning status

Shell

az mysql flexible-server show \

--name YOUR_SERVER_NAME \

--resource-group YOUR_RESOURCE_GROUP \

--query "{state:state, userVisibleState:userVisibleState, provisioningState:properties.provisioningState}"

You want provisioningState = Succeeded and state/userVisibleState = Ready (not Stopped, Updating, Failed, etc.).

2. If the server is simply Stopped, try a start (not restart)

Shell

az mysql flexible-server start \

--name YOUR_SERVER_NAME \

--resource-group YOUR_RESOURCE_GROUP

restart requires the server to be running; start is the correct action from Stopped.

3. See what Azure is doing in the background (Activity Log)

Identify the resource ID:

Shell

az mysql flexible-server show \

--name YOUR_SERVER_NAME \

--resource-group YOUR_RESOURCE_GROUP \

--query id -o tsv

Then pull recent operations:

Shell

az monitor activity-log list \

--resource-id /SUBSCRIPTIONS/<SUB_ID>/RESOURCEGROUPS/<RG>/PROVIDERS/MICROSOFT.DBFORMYSQL/FLEXIBLESERVERS/<SERVER_NAME> \

--max-events 50

Look for any Update, Start/Stop, Patch, Scale with status InProgress or Failed. If one is in progress, you’ll need to let it finish; if failed, see the error details.

4. Check for locks blocking state changes

Shell

az resource lock list \

--resource-name YOUR_SERVER_NAME \

--resource-group YOUR_RESOURCE_GROUP \

--resource-type "Microsoft.DBforMySQL/flexibleServers"

Remove any non‑essential lock:

Shell

az resource lock delete --ids LOCK_ID

5. If you recently tried to scale or update, back off and retry after state clears

While provisioningState != Succeeded, update operations will continue to throw OperationNotAllowedForNonSucceededServer.

Once the server is Ready, you can safely retry:

Shell

az mysql flexible-server update \

--name YOUR_SERVER_NAME \

--resource-group YOUR_RESOURCE_GROUP \

--sku-name GP_Gen5_4

6. Use wait to avoid racing the backend

If you triggered a start:

Shell

az mysql flexible-server wait \

--name YOUR_SERVER_NAME \

--resource-group YOUR_RESOURCE_GROUP \

--created # or --updated depending on your last operation

This waits until Azure reports the state change rather than immediately issuing the next command.

7. Check service health for your region

Sometimes stuck operations correlate with platform incidents. Verify:

Azure Status: https://status.azure.com/

If you see a regional advisory affecting Azure Database for MySQL – Flexible Server, avoid repeated mutations until it’s resolved.

8. If provisioning State = Failed or the server stays Stopped with “busy” for >30–60 minutes

Capture the Activity Log correlation IDs and error details.

If these steps don’t resolve the issue, please send us a private message with:

• Subscription id:
• Tenant id:
• Your registered email id:
• Resource URI of the server:
• Time zone:
• Tracking id:

We will investigate further and help get your server unstuck

Regards,
Vrishabh