Azure-docs: Speech to Text Webhook stopped getting pinged

[rajatb94]

Today suddenly my registered webhook is not getting pinged on a Successful Transcription. Earlier it was working fine. However, all webhook endpoints such as creation, deletion, listing are working perfectly.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: abdefe38-e71e-4e84-d504-a47351bc1325
• Version Independent ID: acea917c-e0f6-689f-09be-97db2524a466
• Content: Webhooks - Speech Services
• Content Source: articles/cognitive-services/Speech-Service/webhooks.md
• Service: cognitive-services
• Sub-service: speech-service
• GitHub Login: @PanosPeriorellis
• Microsoft Alias: panosper

[Karishma-Tiwari-MSFT]

@rajatb94 Thanks for your question. Please provide us with the link to the documentation you are referring to so we can better assist.

[rajatb94]

Hi Madam/Sir,
I m referring to this docs. Earlier my webhook was perfectly-getting called
on speech to text batch task completion but when I checked it yesterday It
was not.

NOTE: PING and TEST APIs of Webhook are working

https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/webhooks

On Sun, Jul 21, 2019 at 11:24 PM Karishma Tiwari - MSFT <
[email protected]> wrote:

@rajatb94 https://github.com/rajatb94 Thanks for your question. Please
provide us with the link to the documentation you are referring to so we
can better assist.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/35553?email_source=notifications&email_token=ADA3EETBKDI5I6ITKVL2QCDQASPFFA5CNFSM4IFSXYS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2OIMUY#issuecomment-513574483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADA3EESKECRLN4JVNF5CJJ3QASPFFANCNFSM4IFSXYSQ
.

[rajatb94]

I have found the issue. You guys have not launched docs of version 2.1 of the Batch Transcription APIs and currently, only v2.0 is present. However, the Webhook APIs have a version 2.1. Earlier Webhook v2.1 was compatible with Batch Transcription v2.0 but suddenly the compatibility went off. I fixed the issue by just trying the version 2.1 in Batch Transcription Endpoints and I modified the request format using the error response I was getting with this new undocumented version.

[Karishma-Tiwari-MSFT]

Thanks for sharing the doc link. I have added the right team to take a look and update the doc or consult the product team as needed.

[YutongTie-MSFT]

@rajatb94 Thank you Rajat, I will update the document.

[rajatb94]

Thanks a lot for understanding the issue. i will be happy to see an updated
docs to get my team a stable reference .

On Wed, 24 Jul 2019, 23:57 YutongTie-MSFT, [e-mail] wrote:

@rajatb94 https://github.com/rajatb94 Thank you Rajat, I will update
the document.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/35553?email_source=notifications&email_token=ADA3EESLDQ7TEMF73VJ6BJLQBCNH7A5CNFSM4IFSXYS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2XGOYQ#issuecomment-514746210,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADA3EEQ7Z5DLN2PLFG5MM4LQBCNH7ANCNFSM4IFSXYSQ
.

[YutongTie-MSFT]

@PanosPeriorellis Hi Panos, I can not fix the whole part so I reassign this issue to you. Could you please take a look and update the document and API references?

@rajatb94 Hi Rajat, I assigned this issue to doc author for completely update. Thank you for your feedback again.

[zacktayl]

Any update on this issue? This is blocking my work as well.

@rajatb94 - Would you mind sharing your findings on the 2.1 api?

[rajatb94]

Any update on this issue? This is blocking my work as well.

@rajatb94 - Would you mind sharing your findings on the 2.1 api?

Hi @zacktayl,
Speech Batch Transcription Docs is currently there for v2.0. You will have to use v2.1 which is not mentioned. I am sharing u the end point URL with the request format
URL
/api/speechtotext/v2.1/transcriptions

REQUEST (POST)

{
                "RecordingsUrls": [<RECORDING_URL>],
                "models": [],
                "locale": "en-US",
                "name": "Transcription using locale en-US",
                "description": "An optional description of the transcription.",
                "properties": {
                    "ProfanityFilterMode": "Masked",
                    "PunctuationMode": "DictatedAndAutomatic"
                }
 }

NOTE:

1. Other End Points will remain similar. You just need to replace v2.0 with v2.1 in request URL.
2. Even the Transcription Result format has been changed. To get the new one you can just use the transcription status API of v2.0 (by changing 2.0 --> 2.1)

[rajatb94]

Any update on this issue? This is blocking my work as well.

@rajatb94 - Would you mind sharing your findings on the 2.1 api?
Please feel free to ping me in case u have any doubt.

[zacktayl]

Thanks, @rajatb94!

My webhook is now working again!

@Karishma-Tiwari-MSFT - This is a little concerning that apis are being changed/deprecated without any notice to devs/companies who rely on these apis. Is there somewhere that documents api deprecation timelines? Or maybe an email listing that I could be added to?

[rajatb94]

Thanks, @rajatb94!

My webhook is now working again!

@Karishma-Tiwari-MSFT - This is a little concerning that apis are being changed/deprecated without any notice to devs/companies who rely on these apis. Is there somewhere that documents api deprecation timelines? Or maybe an email listing that I could be added to?

Welcome @zacktayl ... Its my pleasure to be of some help..
I m still waiting for a stable response from Azure team.

[Karishma-Tiwari-MSFT]

Thanks, @rajatb94!

My webhook is now working again!

@Karishma-Tiwari-MSFT Karishma Tiwari FTE - This is a little concerning that apis are being changed/deprecated without any notice to devs/companies who rely on these apis. Is there somewhere that documents api deprecation timelines? Or maybe an email listing that I could be added to?

@YutongTie-MSFT @PanosPeriorellis Can you please share the information asked by the customer above? Thanks :)

[YutongTie-MSFT]

@PanosPeriorellis Hi Panos, do you have any update for this issue? Thank you

[rajatb94]

On 20th Aug 2019, the Batch Transcription stopped working (for the v2.1 undocumented API). The scheduled jobs did not switch to the status "Running", instead they stuck at "Not Started". I am not sure how and who is managing this service but as a customer, I invest money to use your services which are pretty inconsistent. Don't you think it is wrong from your business perspective?. It even has been almost 1 month since this issue was raised and still, there is no progress.

[ekurutepe]

I'm building a speech to text feature based on this service for my customers and I could only get the webhooks working with the workaround @rajatb94 posted two months ago on this thread! I understand different modules can have different releases cycles and all but two months? Not even the docs are updated.

[rajatb94]

Hi Microsoft guys I got a really quick fix for you. Just change the issue title to "Beating Head Against The Wall".

[YutongTie-MSFT]

@rajatb94 @ekurutepe Hi Rajat and Engin, I am very sorry for the delay. I have reached out to the author again for confirming and it will be updated later. Thanks a lot and sorry for all inconveniences.

[BadFame]

Hi,

First of all, I have been working to get the Webhook setup and got it to work just fine using Speech Services V2.1 as suggested in this thread. If it wasn't for this thread, I wouldn't have known at all on how to fix it since v2.1 speech services is not documented anywhere. Only 2.0 for the batch transcription and 2.1 for the Webhook.

Secondly, the Webhook stopped calling my callback URL this morning. I have even deleted the Webhook and re-created it again. But this time around the Web-hook, on creation of itself, is not even pinging the URL provided in the config property at all. Much less on 'TranscriptionCompletion' events. Anyone experiencing something like that? Below were the steps to follow:

Step 1:
POST: https://{REGION}.cris.ai/api/speechtotext/v2.1/transcriptions/hooks
HEADER: SUBSCRIPTION KEY header
BODY:
{
"configuration": {
"url": "https://webhook.site/SOMEPATH"
},
"events": [
"TranscriptionCompletion"
],
"active": true,
"name": "SOMENAME",
"description": "This is a Webhook created to trigger an HTTP POST request when my audio file transcription is completed.",
"properties": {
"Active" : "True"
}

}

STEP2:
RESPONSE:
{
"id": "SOMEID FROM WEBHOOK SERVICE",
"name": "SOMENAME",
"description": "This is a Webhook created to trigger an HTTP POST request when my audio file transcription is completed.",
"configuration": {
"url": "https://webhook.site/SOMEPATH"
},
"events": [
"TranscriptionCompletion"
],
"active": true,
"pingUrl": "https://{REGION}.cris.ai:443/api/speechtotext/v2.1/transcriptions/hooks/SOMEID FROM WEBHOOK SERVICE/ping",
"testUrl": "https://{REGION}.cris.ai:443/api/speechtotext/v2.1/transcriptions/hooks/SOMEID FROM WEBHOOK SERVICE/test",
"apiVersion": "v2.1",
"createdDateTime": "2019-09-26T18:36:51Z",
"lastActionDateTime": "2019-09-26T18:36:51Z",
"status": "Succeeded",
"properties": {
"Active": "True"
}
}

STEP3:
No ping to config URL end-point upon creation, and No callback upon "TranscriptionCompletion" while using '/api/speechtotext/v2.1/transcriptions' batch Transcription API using the same subscription.

[rajatb94]

Hi @BadFame,
I just tested my system after reading your comment. You are correct, I think even the v2.1 has stopped working. I think we should try v2.2 and wait for even that to stop working #lol

[BadFame]

@rajatb94,

I am just glad that am not the only one experiencing an issue...

This is a cool feat from the service... I wouldn't like to go and create a polling routine. like in the old days...

[PanosPeriorellis]

took the webhook documentation offline until we release v3

[PanosPeriorellis]

sign-off

[erhopf]

please-close