Azure Database for PostgreSQL Flexible Server control-plane failure: database ARM GET returns 502 ServerUnableToRetriveDat

Question

Subject

Azure Database for PostgreSQL Flexible Server control-plane failure in Sweden Central: database ARM GET returns 502 ServerUnableToRetriveData,

server restart returns 500 InternalServerError

Severity / Impact

Our dev deployment is blocked because Terraform can no longer manage the PostgreSQL Flexible Server database resource. The issue started on March

23, 2026. Acceptance does not have the same issue.

Resource Details

• Subscription ID: 89f10dda-dae8-4293-ba07-bac583f6fdaf
• Resource Group: qontactai-dev-rg
• Server Name: qontactai-dev-pg
• Database Name: qontactai-dev-pgdb
• Region: Sweden Central

Issue Summary

Since March 23, 2026, reads of the PostgreSQL Flexible Server database child resource are failing via Azure ARM with 502 Bad Gateway and error

code ServerUnableToRetriveData.

This blocks Terraform on resource:

Microsoft.DBforPostgreSQL/flexibleServers/databases

for:

/subscriptions/89f10dda-dae8-4293-ba07-bac583f6fdaf/resourceGroups/qontactai-dev-rg/providers/Microsoft.DBforPostgreSQL/flexibleServers/

qontactai-dev-pg/databases/qontactai-dev-pgdb

We did not make any recent server configuration changes before the problem started.

Acceptance environment does not show the same behavior, so this appears scoped to this specific server/database or backend shard rather than our

Terraform code.

Observed Behavior

1. Terraform fails on the database resource with:

unexpected status 502 (502 Bad Gateway) with error:

ServerUnableToRetriveData: Server encountered an issue while trying to retrieve some data. Try again later.

2. Azure CLI reproduces the same failure:

az postgres flexible-server db show \

--resource-group qontactai-dev-rg \

--server-name qontactai-dev-pg \

--database-name qontactai-dev-pgdb \

-o jsonc

Result:

(ServerUnableToRetriveData) Server encountered an issue while trying to retrieve some data. Try again later.

Code: ServerUnableToRetriveData

Message: Server encountered an issue while trying to retrieve some data. Try again later.

3. Direct ARM call to the stable API version also fails:

az rest \

--method get \

--uri

"https://management.azure.com/subscriptions/89f10dda-dae8-4293-ba07-bac583f6fdaf/resourceGroups/qontactai-dev-rg/providers/Microsoft.DBforPostgreSQL/flexibleServers/qontactai-dev-pg/databases/qontactai-dev-pgdb?api-version=2024-08-01"

Result:

Bad Gateway({"error":{"code":"ServerUnableToRetriveData","message":"Server encountered an issue while trying to retrieve some data. Try again

later."}})

4. The server resource itself is readable and reports state: "Ready":

az postgres flexible-server show \

--resource-group qontactai-dev-rg \

--name qontactai-dev-pg \

-o jsonc

Relevant output:

• state: Ready
• location: Sweden Central
• sku: Standard_B2s
• version: 15

5. We attempted a restart as a low-risk recovery action, but that also failed:

az postgres flexible-server restart \

--resource-group qontactai-dev-rg \

--name qontactai-dev-pg

Result:

(InternalServerError) An unexpected error occured while processing the request.

Tracking ID: '789cf2ec-50a5-4541-a057-a2a7196121c1'

Request IDs / Correlation IDs

Database ARM GET request IDs:

• 9ebfaf20-c4cf-41fd-9975-6dbd4c788f52
• 3b930c95-9395-4f80-9243-940439ca102b
• ada30d81-06e9-4e29-adf0-dc327bebd960
• e7bece89-f926-49b7-a89a-2038728101cc

Database ARM correlation IDs:

• c656177d-55c5-4aac-8ee4-7a3f067ffa12
• 097aa6d2-1125-4ee3-b1ab-63f06b0638a2
• c5abbc6c-df64-4913-b592-96cf4a028d7a
• aa69d458-949a-4d2f-8ecd-1b13061d07d1

Restart tracking ID:

• 789cf2ec-50a5-4541-a057-a2a7196121c1

What We Need From Azure Support

Please investigate and repair the backend/control-plane state for this Flexible Server/database resource so that:

• ARM GET on the database child resource succeeds again
• restart/control-plane operations succeed again
• Terraform can resume managing qontactai-dev-pgdb via AzureRM

At this point the problem appears to be in Azure control plane/resource provider behavior for this specific server/database, not in client

tooling, because the failure reproduces through Terraform, Azure CLI, and direct ARM REST.

If useful, I can also compress this into a shorter portal-ready version.

Answer 1

Hi @Gilles Jacobs I've checked your server status from the backend. it is back online and running state.