Event grid failed events through not storing in dead letter queue

Karnavkumar Vyas 1

We want to check failed events will be go on dead letter or not .

We have event grid and webhook(logic app) end point . We added response action with code 400 from logic app .

so we assume that events will be moving in to dead letter queue .

But we couldn't see any specific events on dead letter storage .

Note : We have configuration in place for dead letter queue .

Anonymous

2022-12-02T14:50:54.813+00:00

what trigger are you using for the Logic App? If you use one that is marked auto-complete it will be removed from the queue immediately upon logic app invocation. If you use peek-lock it won't be removed until you 'Complete' the message in the logic app. You may want to 'Abandon' the message if processing fails so the lock is removed, or the lock will be removed when the timeout is reached. You have to decide how to handle that. The items I mentioned are part of the Service Bus connector in Logic Apps.
Karnavkumar Vyas 1 Reputation point

2022-12-03T04:55:12.22+00:00

Thanks MildenbergerScott for response ..

We are using strandard logic app work flow with http trigger. No such setting enabled .
Anonymous

2022-12-05T13:38:01.543+00:00

Sorry, I missed that this is a webhook, never used that method. only thought I have is what if you use the 'Terminate' to fail the logic app?
Mike Urnun 9,821 Reputation points Microsoft Employee

2022-12-05T22:42:03.087+00:00
Hello @Karnavkumar Vyas - Thanks for reaching out! Based on my understanding, you have the following:

Logic Apps triggers on HTTP request

In the workflow, you publish an event to EG Topic using the Publish Event action

Immediately after publishing an event to the topic, HTTP action sends a request (with an input carrying a 400 status code) to the Topic endpoint.

The expected result is 400 sent to the EG Topic will result in dead-lettered events.

You don't have Service Bus and are not using any of its features such as dead-lettering.

Could you confirm if the above is correct?

1 answer

AdamMarczak 6 Reputation points MVP

2022-12-23T13:47:38.773+00:00

Hey there, the event grid service does not trigger retry policies on following error codes (400 Bad Request, 413 Request Entity Too Large, 403 Forbidden, 404 Not Found). So the events will never land in the dead-letter queue.

You need to return a different error code (example: 500) as those mentioned indicate client errors.

Reference: https://learn.microsoft.com/en-us/azure/event-grid/delivery-and-retry?WT.mc_id=AZ-MVP-5003556#retry-schedule
Please sign in to rate this answer.

1 person found this answer helpful.
shaswat1122 0 Reputation points

2024-11-13T12:44:37.75+00:00

Any ideas how it will response to a error code of 429 and when will it go to the dead lettered event for the following ?
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Event grid failed events through not storing in dead letter queue

1 answer

Your answer