Azure Event Grid 500 An unexpected error has occurred

Question

Ever since migrating from Microsoft.Azure.EventGrid to Azure.Messaging.EventGrid I am receiving multiple occurrences of the following error while publishing events. Does anyone know what the problem could be?

Error response [90d3c2ba-b306-477d-9ef9-f1db5b29cd46] 500 An unexpected error has occurred. Please report the x-ms-request-id header value to our forums for assistance or raise a support ticket. Report '189ae69e-970d-4b21-96b6-9281f200b3b4:3:11/8/2023 2:58:37 AM (UTC)' to our forums for assistance or raise a support ticket. (00.0s) Server:Microsoft-HTTPAPI/2.0 Strict-Transport-Security:REDACTED x-ms-request-id:189ae69e-970d-4b21-96b6-9281f200b3b4 Date:Wed, 08 Nov 2023 02:58:37 GMT Connection:close Content-Length:721 Content-Type:application/json; charset=utf-8

Answer 1

Michael Tims Thanks for working with azure support team regarding this issue. I am sharing the quick summary of the issue so that it benefits others with the similar issues. Please feel free to add if I missed anything.

Update for the community:

After migrating the apps from Microsoft.Azure.EventGrid v3.2.0 to Azure.Messaging.EventGrid v4.20.0, found intermittent 500 errors were occurred but with the default retry policy of EventGridPublisherClientOptions, all retried requests were successful. So, retry mechanism in Azure.Messaging.EventGrid worked as expected. However, the legacy library didn't throw any errors (validated by reverting back to the older version).

The suggestion is to enable diagnostic logging as described in doc: Enable diagnostic logs for Event Grid resources which will help in investigating the issue further. If you observe similar issues, please follow the suggestion and reach out to us for assistance with the details.

I hope this helps.

---

If you found the answer to your question helpful, please take a moment to mark it as Yes for others to benefit from your experience. Or simply add a comment tagging me and would be happy to answer your questions.