They were working just fine before. What are the possible reasons this could’ve happened and how do I fix it?
2 Likes
Note that a webhook notification will fail if:
- it takes longer than 30s to establish a connection to the endpoint (connection timeout)
- it takes longer than 10s to complete the request (read timeout)
Once a webhook notification fails, the system will retry 10 times. If after those retries there’s no success, the endpoint will be auto-muted (= will no longer be used in future), which means that even if the issue causing the failure (eg: notification endpoint temporarily down) is resolved, you’ll need to manually re-activate the webhook notification for it to work again moving forward, as described here: Bitmovin Docs - Encoding FAQ - How can I mute/unmute a Webhook?
2 Likes