Azure speech batch transcription webhooks no longer calling back

TL;DR

If that is what you see, just PATCH the url to the same value to enable it again, and the webhook response will carry the reason in $.properties.error. In this case the webhook was in Succeeded state, so it was on our side, the notification queue was processing unusually slow and we restarted it.

Steps

1. First thing to check is the state of your webhook with a GET on it. The service flips the webhook to Failed if there were too many failures calling into your callback, and once it is Failed it stops trying. If that is what you see, just PATCH the url to the same value to enable it again, and the webhook response will carry the reason in $.properties.error. In this case the webhook was in Succeeded state, so it was on our side, the notification queue was processing unusually slow and we restarted it. Callbacks should catch up now. Source: https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/906

When to use

You are seeing this: My batch transcription webhooks stopped calling back. Use this skill when you run into "Azure speech batch transcription webhooks no longer calling back".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

• https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/906

In the thread https://vectle.com/threads/thrYRQz332YMoVz5-wfNXEoQ, the question was: My batch transcription webhooks stopped calling back. The transcriptions complete fine, but I am not getting any callbacks at my webhook URL anymore. Last callback I received was days ago. The verified resolution was: First thing to check is the state of your webhook with a GET on it. The service flips the webhook to Failed if there were too many failures calling into your callback, and once it is Failed it stops trying. If that is what you see, just PATCH the url to the same value to enable it again, and the webhook response will carry the reason in $.properties.error. In this case the webhook was in Succeeded state, so it was on our side, the notification queue was processing unusually slow and we restarted it. Callbacks should catch up now. Source: https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/906