Share via

Azure Eventgrid throws internal server error to publishers causing delayed events.

Aly SALL 0 Reputation points
2026-02-20T08:55:55.32+00:00

We utilize Azure Eventgrid and are sometimes experiencing service disruptions as events get delayed with approx 30-60 minutes from initial publication time. The Eventgrid resource has all diagnostic features turned on and shows that during these episodes of delayed events, EventGrid logs publishing failures to a storage account with errormessage inputEventFieldCount=, httpStatusCode=InternalServerError, errorType=UnexpectedError, errorMessage=An unexpected error has occurred. Please report the x-ms-request-id header value to our forums for assistance or raise a support ticket.. The publishers them selves does not seem to log or receive the error message from Eventgrid.

Azure Event Grid
Azure Event Grid

An Azure event routing service designed for high availability, consistent performance, and dynamic scale.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Q&A Assist
    2026-02-20T08:56:04.4566667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    Experiencing internal server errors (HTTP status code 500) with Azure Event Grid can lead to delays in event publishing. This error indicates that there is an issue on the server side that is preventing the successful processing of requests. Here are some steps you can take to troubleshoot and mitigate these issues:

    1. Check Metrics and Diagnostic Logs: Since you have diagnostic features turned on, review the metrics and logs for your Event Grid namespace. This can provide insights into the frequency and nature of the errors occurring during the delays.
    2. Review the Request ID: The error message suggests reporting the x-ms-request-id header value. This ID can help Azure support identify the specific request that failed, allowing for more targeted assistance.
    3. Event Delivery and Retry Policies: Understand that Event Grid provides durable delivery and retries messages based on a fixed schedule. If an event is not acknowledged, Event Grid will attempt to deliver it again. However, if the underlying issue persists, this can lead to delays.
    4. Consider Scaling: If your application is experiencing high load, consider whether your Event Grid setup is adequately scaled to handle the volume of events being published.
    5. Contact Support: If the issue continues, raising a support ticket with Azure may be necessary, especially if you can provide the x-ms-request-id for further investigation.

    By following these steps, you can better understand and address the internal server errors impacting your event publishing.

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.