Azure Durable Function Status Query Endpoint randomly refuses Connection

Fabian Franz 31 Reputation points
2023-08-02T09:21:44.14+00:00

I have an Azure Durable Function (Functions Platform V4), hosted on Windows in a Premium Plan (EP1) in Azure located in West Europe.

The Client Function gets triggered by a React app, that makes HTTP calls to it. To show our users the result of the orchestration, the client calls starter.CreateCheckStatusResponse() on the instance of IDurableOrchestrationClient.

The React app code reads the statusQueryGetUrl from the clients response, and polls the provided query endpoint.

I recently fixed the issue, that (even though we are running on a Premium Plan) the query endpoint sometimes returns an HTTP Status Code 503 - Service Unavailable.

However, sometimes the Function just seems to refuse the connection and does not provide any status code, as shown in the screenshot below:

User's image

I honestly don't know where to find the issue, and on my opinion neither this nor the response of a Http Status Code 503 - Service Unavailable should happen, since Azure Functions running on a Premium Plan are guranteed to be available 99.95% regarding the SLA.

I have executed about 10 requests yesterday on our production system, and for 6 of them this happened.

When I look through the Diagnose and Solve Problems tab within the Azure Portal, it doesn't show me any issues.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
Azure Static Web Apps
Azure Static Web Apps
An Azure service that provides streamlined full-stack web app development.
Developer technologies | .NET | Other
Developer technologies | C#
Developer technologies | C#
An object-oriented and type-safe programming language that has its roots in the C family of languages and includes support for component-oriented programming.
{count} votes

Your answer

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