@roger_zander@SignalR Hi Roger, this is Ken from Azure SignalR Service team. Sorry for the inconvenience to your SignalR instance, do you mind share more information about this (like your resource ID) so we can take a look at our side?
@digitalKahuna6 Hi Satish, do you have any detailed error messages to share? And if you can share your SignalR resource name I can help take a look at our backend to see if there is anything wrong.
@ScragglyNark Yes, severless mode doesn't support connection events right now but we are working on some new features which allow these events to be sent in a severless scenario. So this will become possible in future.
Real-time + Serverless on @Azure: Azure @SignalR Service binding for Azure Functions is now GA! Now you can use C#, JS/TS, Java ... to build serverless real-time application on Azure. Check out https://t.co/SQtZhyyLNx
@shibayan@shangzd So for your case if you're using Azure functions binding, you should use serverless mode (assume your app is purely serverless). Classic mode is only there for compatibility. If your app relies on the old behavior you can keep using that mode.
@shibayan@shangzd For example, server connections may get dropped for some reason. It's not easy for user to discover it as clients can still connect in a serverless mode. That's why we came up with the two new modes where the behaviors are more clearly defined.