deserializationPolicy.ts error when handling 400s

[xtreme-sameer-vohra]

• Package Name: @azure-rest/core-client
• Package Version: 1.4.0
• Operating system: Mac Ventura
• nodejs
  • version: v23.2.0
• browser
  • name/version: n/a
• typescript
  • version: ^5.0.4
• Is the bug related to documentation in
  • README.md -> Call Automation Live Transcription
  • source code documentation
  • SDK API docs on https://learn.microsoft.com

Describe the bug
When running src/app.ts, after an incoming call is handled, upon receiving some call events, the application crashes

To Reproduce
Steps to reproduce the behavior:

1. Setup callautomation live transcription demo
2. Answer an incoming call and stay on the line for > 30 s

Error in console output

/azure-live-transcription/node_modules/@azure/core-client/src/deserializationPolicy.ts:255
  const error = new RestError(initialErrorMessage, {
                ^
RestError: IDX23010: Lifetime validation of the signed http request failed. Current time: '11/14/2024 7:50:08 PM' UTC, signed http request is valid until: '11/14/2024 6:43:34 PM' UTC.
    at handleErrorResponse (/Users/sameer/workspace/azure-live-transcription/node_modules/@azure/core-client/src/deserializationPolicy.ts:255:17)
    at deserializeResponseBody (/Users/sameer/workspace/azure-live-transcription/node_modules/@azure/core-client/src/deserializationPolicy.ts:159:43)
    at processTicksAndRejections (node:internal/process/task_queues:105:5) {
  code: undefined,
  statusCode: 400,
  details: {}
}

OR

azure-live-transcription/node_modules/@azure/core-client/src/deserializationPolicy.ts:255
  const error = new RestError(initialErrorMessage, {
                ^
RestError: Invalid request
    at handleErrorResponse (/Users/sameer/workspace/azure-live-transcription/node_modules/@azure/core-client/src/deserializationPolicy.ts:255:17)
    at deserializeResponseBody (/Users/sameer/workspace/azure-live-transcription/node_modules/@azure/core-client/src/deserializationPolicy.ts:159:43)
    at processTicksAndRejections (node:internal/process/task_queues:105:5) {
  code: '400',
  statusCode: 400,
  details: {
    error: { code: '400', message: 'Invalid request', details: [Array] }
  }
}

Expected behavior
Demo app to not crash

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[github-actions]

@deyaaeldeen @jeremymeng @joheredi @maorleger @mpodwysocki @timovv @xirzec

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[xtreme-sameer-vohra]

Specifically narrowed the issue down to https://github.com/Azure-Samples/communication-services-javascript-quickstarts/blob/main/callautomation-live-transcription/src/app.ts#L89

And just as a cheap retry, tried to recreate a new client and retry the answerCall command.

try {
	answerCallResult = await acsClient.answerCall(incomingCallContext, callbackUri, answerCallOptions);
}
catch(error) {
	console.log(`ERROR IN ANSWERING CALL: ${error}`);
	await createAcsClient();
	answerCallResult = await acsClient.answerCall(incomingCallContext, callbackUri, answerCallOptions);
}

That resulted in another exception being thrown at the 2nd answerCall with the new acsClient

[timovv]

Hi @xtreme-sameer-vohra, thank you for the report. This doesn't appear to be an issue with the core-client package -- the deserializationPolicy will throw a RestError whenever an unsuccessful (i.e. non-2xx) status code is received from the service. This includes the 400 status code that you are seeing.

I will tag this issue with the Communication label so that the ACS folks can help you with the underlying reason as to why the service might be responding with a 400 status here. Thanks for your patience!

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @acsdevx-msft.

[xtreme-sameer-vohra]

Thanks @timovv