Share via

Azure PostgreSQL Flexible Server stuck in "Dropping" state

Donatas Zubavičius 20 Reputation points
2025-04-24T11:33:55.2933333+00:00

Hi Team,

We are experiencing an issue with a PostgreSQL Flexible Server in Azure that is stuck in a broken "Dropping" state.

We attempted to delete the server, but now:

It shows “Dropping” in Azure Portal

Clicking it throws: "Cannot read properties of undefined (reading 'createdAt')"

Delete through resource group returns error thar resource was not found.

This is similar to: https://learn.microsoft.com/en-us/answers/questions/2258929/azure-postgresql-flexible-server-stuck-in-dropping?source=docs

I see that deployment it self failed:

The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Canceled'.

Is there any way to resolve this?

Thanks!

Azure Database for PostgreSQL
0 comments
Accepted answer
  1. Saraswathi Devadula 2,095 Reputation points Microsoft External Staff
    2025-04-24T12:50:53.9533333+00:00

    Hello Donatas Zubavičius

    Thank you so much for your response.

    I am glad to hear that you were able to drop and recreate the server successfully.

    Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others"

    Please click "Accept" the answer as original posters help the community find answers faster by identifying the correct answer.

    Issue: Azure PostgreSQL Flexible Server stuck in "Dropping" state

    Resolution: Your initial deployment failed because it was cancelled, which caused the DB instance to get stuck. You retried the deployment, which removed the instance from the “dropping” state, and it was successfully removed.

    After that, you were able to delete and recreate everything without issues.

    I hope this has been helpful.

    Your feedback is important so please take a moment to accept answers. If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!
    User's image

    Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer.

     

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Donatas Zubavičius 20 Reputation points
    2025-04-24T12:04:44.0333333+00:00

    Managed to fix this.
    My initial deployment failed because it was canceled (probably me deleting it?), which caused the DB instance to get stuck.
    I retried the deployment, which removed the instance from the “dropping” state, and it was successfully removed.

    After that, I was able to delete and recreate everything without issues.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.