Azure Cosmos DB for MongoDB stuck in Updating state since past 2 days after performing scale-up operation

Question

Azure Cosmos DB for MongoDB stuck in Updating state since past 2 days after performing scale-up operation

Pulkit 20

Hi,

As mentioned in title, a scale up operation was performed (Free to M10) on the Azure CosmosDB on 22/6/26, the status of the DB became 'Updating' since then.
Unable to perform any other scale operations or even create a new instance ever since.

No error or excess resource use (Memory, CPU, IOPS) is observed.

Since there is no option to restart the service, how to resolve the issue?

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Pulkit hi, thx for sharing urs issue here at Q&A portal,

the scale-up operation got stuck in the Cosmos DB control plane.

If the account has been in Updating for 2 days after Free -> M10, that’s not normal workload pressure. CPU/memory/IOPS won’t really explain it, bc the stuck state is about the management operation, not the database engine itself.

There’s no customer-side restart for Cosmos DB for MongoDB. While the account is stuck in Updating, new scale operations usually get blocked bc the RP still thinks the previous operation is running.

Grab the Activity Log entry for the original scale-up and copy the correlation ID / operation ID. That’s what MS needs to find the stuck backend operation.

az monitor activity-log list \

--resource-id '<cosmos-resource-id>' \

--offset 3d

Best move rn is open a support case under Cosmos DB and ask them to clear or recover the stuck scale operation from the backend. Include resource ID, region, old tier, target tier M10, UTC start time, and the Activity Log correlation ID.

I wouldn’t keep retrying scale changes. It won’t unstick the original operation and can make the history messier. This needs Cosmos DB RP/backend cleanup.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal