Hi,
We have a Teams chat bot (aka root bot) that is currently connected to a Skill Dialog bot. When we deploy the root bot and the skill dialog bot to the same app service plan with instance count set to 1, both bots perform per expectations.
When we deploy the root bot to its own app service plan with instance count set to 1 and the skill dialog bot with instance count set to 1, both bots perform per expectations.
When we deploy the root bot to its own app service plan with instance count set to 2 and the skill dialog bot with instance count set to 2, we start seeing 500 gateway errors. We enabled App Insights and the visualization showed us that communication from the root bot to the skill dialog bot and vice versa would break down and throw the 500 errors.
When we deploy the root bot and the skill dialog bot to the same app service plan but have the instance count set to 2, we are also seeing 500 gateway errors.
Internally, we suspected that load balancing amongst the instances could be why we are getting the 500 errros. We found a post on Stack Overflow (
https://stackoverflow.com/questions/49651539/how-azure-load-balances-scaled-out-app-service-plan) which seemed to be related to our problem. Since ARR is enabled by default for our web app services, session affinity does not seem to be the issue here.
Has anyone come across the same behavior? Any advice?
Thank You
