Chenyang Liu

Retry makes sense when the request is totally failed. Like socket failure and we don't get any http response. That can be put on our roadmap.

Your function is not correct to handle message. You need to add a function with `SignalRTrigger` to handle `connection.InvokeAsync("JoinGroup", sessionId)` Please refer document https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-signalr-service-trigger?tabs=csharp and sample https://github.com/aspnet/AzureSignalR-samples/tree/main/samples/BidirectionChat

ConnectionId is not mandatory and adding user to group should work. However, the differences between adding user to group and adding connection to group is the previous one is async...

No difference in the library but in the SignalR Service side.

@ispysoftware Although connections are dropped during scaling, it's not happening suddenly. The higher unit count you're using, the total progress will be longer. You can think it as a rolling...

@alexveya I'm now working on that improvement, but it can't be very fast as it has a lot of work to do. As I know, scaling shouldn't close all the...

@alexveya Could you give me you `ResourceId`, thus I can dig deep for you. Waiting for your email.

I will add `Free` to document. You can use `Free_F1` to create a free instance.

Did you get some log when triggering functions from Azure Function side or client side. Here's some possible logs that implies some issues 1. Totally not logs from function or...

@stemixreal If you're using class-based model. You need to use non-static method. And the method name should be **OnConnected** rather than FunctionName. Please refer to https://github.com/aspnet/AzureSignalR-samples/blob/9c16f7cc98ef38b8433251b2466ecd5bd0746418/samples/BidirectionChat/csharp/Function.cs#L37