Darren Jefford

Dismiss works - restart doesn't do anything.

Whenever you create/deploy a new Bot. Once for dev and again for azure

I'm not quite so sure this is a feature-request, the previous runtime worked as expected in this area so this is a regression from where we were before? I believe...

Any volunteers for some documentation steps so developers can at least work around this ahead of R14?

** UPDATE ** Did some digging as per this: https://github.com/microsoft/BotFramework-Composer/blob/ef424c5583d9c2813f4b7255201d912ccc770696/Composer/packages/server/schemas/sdk.en-US.schema By hand I updated my recognizer configuration in recognizers folder to include following (not clear if Composer surfaces this anywhere)...

Hmmm :-) So, the disambiguation trigger has existed since at least Composer 1.2 released in November last year (so pre-orchestrator). From the discovery of `includeAllIntents` not being set it would...

@cwhitten Wasn't entirely sure precisely where to put the settings so tried both approaches: ```json "luis": { "authoringEndpoint": "", "authoringRegion": "westus", "defaultLanguage": "en-us", "endpoint": "", "environment": "composer", "name": "djCoreWithLanguage", "authoringKey":...

Sorry, by switching between Bots I meant different bot projects