Webhook for encoding error not being fired when an encoding has failed

Support
, ,
1

We have two webhooks set up:

  • eventType: Finished
  • eventType: Error

We need to know when an encoding has failed on our side, so we’re trying to test that the webhook is being fired as expected.

In order to do this, we’re initiating an encoding with a corrupted .mp4 file, and we get the error in Bitmovin during encoding as we expect.

However, the request to our API doesn’t seem to be fired since it doesn’t show up in our logs.

One thing to note here is that when we check the webhook state history, it seems to be that it was fired correctly since we get the following response:

{
   "id":"<id here>",
   "state":"FIRED",
   "triggeredAt":"2023-12-07T11:39:26Z",
   "resourceId":"<resource id here>",
   "notificationId":"<notification id here>",
   "muted":"false"
}

Any ideas what could be the reason for this? Thanks in advance.

2

Hi @gjaguilera

Thanks for reaching out to us.

I reviewed the logs and observed that when our encoder tried to trigger the error webhook to your endpoint, it was unreachable. We made 10 retry attempts, but each time resulted in an HTTP 500 Error.

Also, If the notification delivery fails 10 times in a row, the webhook notification will be auto-muted. This means that the API will no longer attempt to deliver any events to that webhook until the user resolves the endpoint issue and unmutes it through the API.

Document Reference - How can I mute/unmute a Webhook?