Deployment on Multiple Instances

[hemantkathuria]

I am using Asp.Net host with SSE. When I deploy on multiple instances it fails saying session id not found.
When I reduce the instance to 1. It works.
How do I enable multiple instances?

[partychen]

You can try the following two approaches:

1. Update to the latest version:
   Could you please update to the latest version of the SDK? It looks like this issue was fixed in v0.1.0-preview.14.

2. Enable session affinity in Azure App Service:
   If you're deploying the service on Azure, go to the Azure portal, navigate to your App Service → Configuration → General settings, and ensure that Session affinity is enabled.

[hemantkathuria]

@partychen - I think I am on 14 only.
I am not hosting on Azure App Service anymore. It is service fabric. But I want to confirm it session affinity / sticky sessions are must for this SDK to work. Does it have dependency on static variables? Also, may be having a sticky session will not be acceptable to all

[partychen]

@hemantkathuria you should also change the code to support streamhttp .WithHttpTransport(options => { options.Stateless = true; }), it can works on multi-instance scenarios. (options.Stateless = true; is not working with SSE.)

[hemantkathuria]

@partychen Copilot studio as a client still don't support stream http.

I am not using app service to host but I enabled cookie affinity but still no luck. It fails with message "Session Id not found"

[halter73]

It fails with message "Session Id not found"

This can also be the failure mode for an SSE client trying to connect to the Streamable HTTP endpoint. This is making me consider having fallback logic for both the server and client as I describe in this comment on issue #440.

@hemantkathuria Are you trying to connect to "https://myapp.azurewebsites.net"? If so, can you try "https://myapp.azurewebsites.net/sse" and see if that fixes your issue?