Forum Discussion
Bot Framework Dispatch CLI replacement with Orchestrator
- Dec 14, 2021
1.Orchestrator is a local resource, so is deployed to the target environment. It should require significantly less training than a LUIS model, so should really only be updated along with your source code. But yes, since the model is loaded into memory you need to restart the bot.
2.Deploy the trained model to the desired environments
Please go through below doc for implementation details:
https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-tutorial-orchestrator
Thanks,
Nivedipa
------------------------------------------------------------------------------------------------------------------------
If the response is helpful, please click "**Mark as Best Response**" and like it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.
MykolaMedynskiy - We will also check it from our end and let you know.
Could you please elaborate your requirement and share the repro steps if any?
- MykolaMedynskiyNov 19, 2021Copper Contributor
Hey Nivedipa-MSFT,
So the requirements are:
– periodically refresh orchestrator model
– use it in the bot for intent recognition
And the problem is refreshing the model without restarting the application, since the orchestrator model is not a Luis App, as was with Dispatch.
- Nivedipa-MSFTNov 29, 2021
Microsoft
Could you please go through below document if its helped you in any way.
Intent recognition with Orchestrator in Bot Framework Composer | Microsoft Docs
- MykolaMedynskiyDec 01, 2021Copper Contributor
Nivedipa-MSFT we've checked all the documentation and haven't found the way to implement it.
We can see that there is a refresh option, but how to use it and not affect the bot application files? Can it be kept separately from the bot project and be queried via some API?
- Nivedipa-MSFTNov 26, 2021
Microsoft
We are checking this internally.We will get back to you once we have any update.