Hey ! I just deployed my bot on Teams, and this is the first time I test the bot outside of the studio, I won't lie it has been a pretty disapointing experience for now. First the bot's behavior inside the emulator and inside Teams were not the same, and some weird unexpected bugs appeared (Capture cards police is bold and big, flow aren't followed properly, something cards are played multiple times for no reasons.) So I decided that I would test it all out and try to correct the problems, but now I face a bigger problem. While the bot runs fine on the emulator, once I try it on Teams (or the Botpress chat) it timeout VERY often, so often that I can't get to the end of a conversation. This is the error in the logs everytime: "Task timed out after 60.10 seconds" Does anybody know why there is such a difference between the emulator and prod ? It is quite disheartening to think that the bot I built works well inside the studio but is useless in prod, I hope this is some exceptional problem because if everytime I test the bot inside the emulator it doesn't translate in production it will be quite the loss of time. Thanks for any insight !

Hey @bulky-dusk-45106, sorry to hear about all the problems with the teams integration. Could you tell us a bit more about the specific problems you're running into? You mentioned so far: * Unexpected text formatting * Unexpected flow behavior * Repeated messages * 60 second timeout on conversations

It's a bit hard to talk to you about the specific problems because I encountered most of them yesterday and today I can't test it because of the timeout error. But the main surprise I had was that the bot's outputs were quite different from the emulator. One thing I remember is that I have an AiTask that receive the user's question, it then decide wether it returns an answer, or if the question is out of the scope of the bot and returns OOS instead. In the emulator, when the task return OOS, it triggers a transition to some message and close the conversation. The weird thing that only happened inside Teams, is that no matter if the user asked an OOS question or not, the bot would both answer the question AND inside its answer say that the user is OOS (which is not supposed to happen, the bot is supposed to either give an answer or return OOS), and never trigger the OOS transition. I tried to see if this behavior could be replicated inside the emulator but without success, this only appeared inside teams.

that's really interesting! You're right that Teams is simply consuming the bot service. Are you using any user data in your AI tasks? The data might have a different format between web chat and Teams that might be causing different behaviors

That' the only theory I had, but all the data the bot is using is either inputed inside the chat, or are configuration variables that I double checked are the same

is there anything strange turning up in the bot logs?

Well there is the timeout error, besides that I just went to look a the logs and they disapeared. I end up on the No recent logs found page

when you talk to the bot on teams, are there any other strange logs besides the timeout error?

I don't remember seeing any other one, but I can't verify that

That's good news!

Ok I may have a theory for the timeout, I just changed a variable value, and republished the bot. And now I am getting timed out again. So I guess there may be some delay to use the bot, after publishing it again

that's an interesting theory! I don't know enough about the inner workings of the Teams integration to give you anything definitive. But maybe there's a delay period between when you publish the bot on Botpress and when it updates on MS Teams?

Yeah I think something like that is happening

alright, I'll touch base with one of the engineers when they're awak and see if that is plausable

Awesome, thanks

could you also share a screenshot of your bot's flow?

ì have a opensource solution also, same issues. trying botpress to fix some bugs in our repository. maybe together the solution occurs.