key vault event is getting error out after 2 consecutive error

Pallavi Chede 1

I have added event on CertificateNewVersionCreated & received trigger in logic app but after consecutive error occurred in my logic app all the subsequent event in key vault is getting error out.

Mike Urnun 9,786 Reputation points Microsoft Employee

2021-09-09T21:13:12.317+00:00

Hello, @Pallavi Chede - Could you provide more details about your workflow and what it does? Also, please include the error message too.
Mike Urnun 9,786 Reputation points Microsoft Employee

2021-09-13T19:35:59.937+00:00

Hi, @Pallavi Chede - Just following up here, let me if you're able to provide any additional details for us to investigate.
Pallavi Chede 1 Reputation point

2021-09-14T11:37:28.357+00:00

Hello, @Mike Urnun I don't get any error in my azure function only my event get populated in error section of event .

my workflow suppose to get trigger when certificate is got uploaded in key vault & then I want to upload that certificate to service principle .Currently I am trying & testing how I can achieve my requirement so many time I get errors in workflow . when I consecutively get 3 errors in my logic app my azure function event is get error out .
Pallavi Chede 1 Reputation point

2021-09-14T11:38:25.177+00:00

PFA screen shot how my event is getting error out
Mike Urnun 9,786 Reputation points Microsoft Employee

2021-09-15T02:47:59.367+00:00

Hello @Pallavi Chede - Thank you for sharing more info! Could you also share a screenshot of the overall workflow of your Logic Apps? It sounds like you're using the Event Grid connector, and its "When a resource event occurs" trigger in a Logic Apps workflow but the trigger may not be consuming any data at all and failing to start the entire flow?

On another note, if the trigger did indeed fail to consume events from Event Grid, you can check trigger history to troubleshoot the root cause & narrow down the error messages. For exact steps on how to do that, please review: Troubleshoot and diagnose workflow failures in Azure Logic Apps
Pallavi Chede 1 Reputation point

2021-09-16T13:54:03.127+00:00

Hello @Mike Urnun

PFA steps what I did and what error I am getting .132792-step-by-step-logic-app.pdf

1 answer

Mike Urnun 9,786 Reputation points Microsoft Employee

2021-09-20T02:02:33.113+00:00
@Pallavi Chede Thank you for supplying more info! So based on the screenshots, I believe there may be 2 separate issues: (a) 405 error originating from the HTTP 2 action, and (b) what may be an intermittent error on KeyVault which is occasionally failing to start the Logic App workflow. I didn't see anything from your workflow that would indicate that one of these is the cause of the other. As such, it might be better to investigate them independently.

For the error 405 issue, it seems like this error was returned from the endpoint that you're making a request to in the HTTP 2 action of your workflow. Could you confirm it is so and check if you're specifying a valid HTTP method in that request?

For the issue of trigger not starting, since there isn't any data in trigger history, I would look to investigate the upstream services: from Event Grid to KeyVault, but could you confirm if the issue is continuing to occur though? From the screenshot, it looked like the trigger fired 2 times successfully but didn't the 3rd time.
Please sign in to rate this answer.
Pallavi Chede 1 Reputation point

2021-09-20T14:43:33.05+00:00

Hello @Mike Urnun

Yes there are 2 separate issues one is related to 405 error on which I am currently working I raised this ticket for second issue that is after 2 times trigger raised it wont create event 3rd time(if logic app failed for earlier two event ) & I am facing this issue from continuously.

Note - if logic app not failed for any event then event trigger logic app every time

Pallavi Chede 1 Reputation point

2021-09-22T09:46:26.807+00:00

Hello @Mike Urnun

Any update ??

Mike Urnun 9,786 Reputation points Microsoft Employee

2021-09-22T18:25:44.957+00:00

Hello, @Pallavi Chede - Thanks for the follow-up and the additional info. That definitely helps to understand the problem. It's important to note here that Trigger History from Logic Apps lists the number of attempts it has taken to run your workflow. As such, the following are true:

An attempt that didn't actually run your workflow will show under the Trigger History list with a Succeeded status. (On Event Grid, this might show as a failed event delivery)

An attempt that actually ran your workflow will be marked in the Fired column of the Trigger History and distinguished as so.

I want to make sure that you're aware of that behavior and not correlating the error to a successful attempt of the trigger on your Logic App. Can you check and confirm that the issue isn't related to this behavior? You can do so by correlating the timestamp between when the error occurred & when the trigger attempted without firing.

Mike Urnun 9,786 Reputation points Microsoft Employee

2021-09-22T18:31:57.997+00:00

@Pallavi Chede Also, I highly recommend that you enable the Dead-Lettering feature on the implicitly created Event Subscription that facilitates event data to your Logic Apps. That way, you're able to recover events that are failed to get delivered and reprocess them again automatically as part of your regular flow: Set dead-letter location and retry policy

Pallavi Chede 1 Reputation point

2021-09-24T10:00:22.05+00:00

Hello @Mike Urnun

I am aware about this behavior .

I would like to request you can we have a quick call where I can show you by sharing my screen so it might help us to understand issue more clearly .
Sign in to comment

Share via

key vault event is getting error out after 2 consecutive error

1 answer