Eugene

@erquirogasw please ensure you pulled the latest version from main before updating the sums.

This might be platform-related issue. Yarn has an issue with hash persistence across platforms unfortunately.

@ceciliaavila e2e pipeline failure seem unrelated to the PR. You can run e2e tests locally for more details

Should be good to go after related package lock hash updates

@Rekhanjalir are you setting up the channel using PVA experience? Seems unrelated to Composer.

@Tz611 does the bot work locally? If it doesn't this may be the cause. Did you publish straight from the template without any changes?

@SuvithaNair please make sure you have all prerequisites installed. For composer Node.js bots they match the Bot Framework SDK: https://learn.microsoft.com/en-us/azure/bot-service/bot-service-quickstart-create-bot?view=azure-bot-service-4.0&tabs=javascript%2Cvs#prerequisites Please note that Node.js support is experimental. Best use latest...

@Divyasree2104 could you verify if the publishing works after going away from the publishing page and returning back after the error appears? Trying to reproduce this issue on my end

I think the adapter needs updates as I see some other issues with it: https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/issues/547 and the https://github.com/BotBuilderCommunity/botbuilder-community-dotnet/issues/535 seems related Looks like the adapter doesn't function properly, probably due to...

> Shouldn't the bot be resilient in handling its state irrespective of number of events/messages etc triggered? It should. And I believe the issue mentioned is the adapter issue, not...