Why are we getting azure platform error - "Exception encountered when listening to event stream. The HTTP/2 connection faulted" for Time triggered function app?

Anirban Roy Choudhury 20 Reputation points
2025-06-16T09:53:25.6866667+00:00

Why are we getting azure platform error - "Exception encountered when listening to event stream. The HTTP/2 connection faulted" for Time triggered function app? We are seeing this is happening intermittently in every few days.

User's image

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
5,909 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Khadeer Ali 5,990 Reputation points Microsoft External Staff Moderator
    2025-06-17T13:31:02.83+00:00

    @Anirban Roy Choudhury ,

    The error you're seeing — ConnectionAbortedException with "Exception encountered while listening to EventStream. The HTTP/2 connection faulted" — is something that can happen occasionally with Azure Timer-triggered Function Apps.

    To clarify, this is not due to your app logic or any HTTP calls from your side. This message appears when the Azure Function host loses its internal connection to the platform's timer scheduler (which runs over HTTP/2 behind the scenes). This can happen due to things like infrastructure maintenance, cold starts, platform updates, or idle timeout on that internal channel.

    This is usually a transient platform-level event, and the connection is automatically re-established by the Functions runtime. As long as you're not seeing missed executions, this can generally be considered safe to ignore.

    1 person found this answer helpful.
    0 comments No comments

  2. Anirban Roy Choudhury 20 Reputation points
    2025-06-23T09:32:28.5866667+00:00

    Thanks @Khadeer Ali, makes sense. This shouldn't impact much if they are transient. We can close this query now.

    0 comments No comments

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.