Power Platform Community Forum Thread Details

We are experiencing an issue with Microsoft Teams Workflows (Power Automate) where all workflow webhook endpoints are returning HTTP 503 responses.

Environment Details:

Service: Microsoft Teams Workflow / Power Automate
Region/Gateway Cluster: prdil107wus
Issue Start Time: 30-May-2026
Impact: Alerts from our monitoring platform are not being delivered to Teams channels.

Behavior:

Existing workflows that were previously working have stopped processing requests.
Direct POST requests to the workflow webhook URL return HTTP 503.
Multiple workflow endpoints appear to be affected.
The requests successfully reach the Microsoft Power Platform endpoint, but the backend service returns an error.

Test Command:

curl -X POST "<workflow_url>" \
-H "Content-Type: application/json" \
-d '{"text":"test"}'

Response:

HTTP/2 503
Content-Type: application/json

Response Body:

{
  "error": {
    "code": "ServiceTemporarilyUnavailable",
    "message": "The service is temporarily unable to service your request. The tracking Id is '00000000-0000-0000-0000-000000000000'."
  }
}

Response Headers:

x-ms-gateway-clusters: prdil107wus
x-servicefabric: NoRetry
x-ms-service-request-id: 7925da5b-053f-43bb-87bf-df93d6da958f
x-ms-correlation-id: 67402c6c-2376-4d4b-a465-dece4c56db91

Additional Information:

DNS resolution, TLS handshake, and network connectivity are successful.
Workflow URL is valid (not receiving 401 or 403 errors).
Issue occurs when invoking the workflow directly via curl, independent of our application.
We would like to know if there is any ongoing outage or service degradation affecting Teams Workflows / Power Automate webhook triggers in the prdil107wus cluster.

Has anyone else experienced the same issue today, and is there any known Microsoft service incident related to this error?

Thank you.

Categories:

Building flows