samples/ServerlessChatWithAuth/v4-model is broken

[1ycx]

After pressing enter, the chat message disappears. On the deployed function, it logs me in and gives me a similar chat UI, but the messages disappear.

I am using the AzureWebJobsStorage and SignalR connection strings from Azure.

Locally, I see some timeout errors too, not sure what is going on. I did try to debug with an LLM but did not find anything conclusive. Creating an issue for others.

Deployed function -

Local function -

[2025-10-23T04:04:38.137Z] Executed 'Functions.messages' (Failed, Id=a3afc891-6c36-4ea6-9d7e-b81511a37c98, Duration=240007ms)
[2025-10-23T04:04:38.138Z] System.Private.CoreLib: Exception while executing function: Functions.messages. Microsoft.Azure.WebJobs.Script: Failed 
to proxy request with ForwarderError: RequestTimedOut. Microsoft.Azure.WebJobs.Script: The operation was canceled.
[2025-10-23T04:04:38.466Z] Executed 'Functions.messages' (Failed, Id=3e008de0-d50e-4694-85db-3c72ebcdabaf, Duration=240012ms)
[2025-10-23T04:04:38.467Z] System.Private.CoreLib: Exception while executing function: Functions.messages. Microsoft.Azure.WebJobs.Script: Failed 
to proxy request with ForwarderError: RequestTimedOut. Microsoft.Azure.WebJobs.Script: The operation was canceled.
[2025-10-23T04:04:38.665Z] Executed 'Functions.messages' (Failed, Id=5da060e5-c5ab-451b-90bb-ae2e5956b113, Duration=240002ms)
[2025-10-23T04:04:38.666Z] System.Private.CoreLib: Exception while executing function: Functions.messages. Microsoft.Azure.WebJobs.Script: Failed 
to proxy request with ForwarderError: RequestTimedOut. Microsoft.Azure.WebJobs.Script: The operation was canceled.
[2025-10-23T04:04:38.854Z] Executed 'Functions.messages' (Failed, Id=dabd1377-d162-4908-99a0-27f230349bcf, Duration=240013ms)
[2025-10-23T04:04:38.855Z] System.Private.CoreLib: Exception while executing function: Functions.messages. Microsoft.Azure.WebJobs.Script: Failed 
to proxy request with ForwarderError: RequestTimedOut. Microsoft.Azure.WebJobs.Script: The operation was canceled.
[2025-10-23T04:04:38.992Z] Executed 'Functions.messages' (Failed, Id=a307a73e-f433-439c-8d86-ae52d773b10b, Duration=240015ms)
[2025-10-23T04:04:38.993Z] System.Private.CoreLib: Exception while executing function: Functions.messages. Microsoft.Azure.WebJobs.Script: Failed 
to proxy request with ForwarderError: RequestTimedOut. Microsoft.Azure.WebJobs.Script: The operation was canceled.
[2025-10-23T04:04:39.152Z] Executed 'Functions.messages' (Failed, Id=d3a21207-6bcb-446f-8947-d301abf0565a, Duration=240015ms)
[2025-10-23T04:04:39.153Z] System.Private.CoreLib: Exception while executing function: Functions.messages. Microsoft.Azure.WebJobs.Script: Failed 
to proxy request with ForwarderError: RequestTimedOut. Microsoft.Azure.WebJobs.Script: The operation was canceled.
[2025-10-23T04:04:39.264Z] Executed 'Functions.messages' (Failed, Id=3950e965-ff0d-466d-a022-391f3b295178, Duration=240008ms)
[2025-10-23T04:04:39.265Z] System.Private.CoreLib: Exception while executing function: Functions.messages. Microsoft.Azure.WebJobs.Script: Failed 
to proxy request with ForwarderError: RequestTimedOut. Microsoft.Azure.WebJobs.Script: The operation was canceled.
[2025-10-23T04:08:36.428Z] Executed 'Functions.messages' (Failed, Id=74a1686f-2f4f-4407-86e0-a185e601414c, Duration=240004ms)
[2025-10-23T04:08:36.429Z] System.Private.CoreLib: Exception while executing function: Functions.messages. Microsoft.Azure.WebJobs.Script: Failed 
to proxy request with ForwarderError: RequestTimedOut. Microsoft.Azure.WebJobs.Script: The operation was canceled.
[2025-10-23T04:08:37.660Z] Executed 'Functions.messages' (Failed, Id=1295f841-3268-40cf-a008-3568b1ac088c, Duration=240005ms)
[2025-10-23T04:08:37.661Z] System.Private.CoreLib: Exception while executing function: Functions.messages. Microsoft.Azure.WebJobs.Script: Failed 
to proxy request with ForwarderError: RequestTimedOut. Microsoft.Azure.WebJobs.Script: The operation was canceled.

[Y-Sindo]

The error message above indicated that your SignalR Service instance was not in 'Serverless ' mode. You should set the service mode to `Serverless` when you created the resource or switch to `Serverless` mode after creation. The following screenshot shows how to switch the mode on Portal.

[1ycx]

Interesting. I did switch it to serverless mode when I tried and took that screenshot. (Free_F1 instance).
I had also tried with a new Standard_S1 instance which was created with serverless mode, only to be in a similar situation.

Thanks for getting back, I'll see if I can retry with a fresh set of everything.

[Y-Sindo]

Could you send your resource ID to my email zityang @ microsoft.com for me to check your resource?