Answered

Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

Like (2) Share

Report

Posted on 14 Oct 2020 11:27:36 by Community Power Pla...

I'm working on a PVA bot that brings in a QnA knowledge base via the MS Flow connector and feeds into Teams.

I've encountered this issue a few times today after publishing updates to the bot and testing it within Teams and also the testing chat window within the PVA environment. I can't see any issues anywhere, I have a feeling this is just that it's slow to push the updates to the channels that the bot is working in but can anybody confirm this?

Categories:

General

All responses (27)

Answers (1)

zafarshamsi 85 on 23 Feb 2024 at 06:21:17

Like (0)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

As I observed during the issue, it's due to session of web browser expire or the connection issue, when I refreshed the page issue also resolved.
jbonomo 44 on 22 Feb 2024 at 20:11:12

Like (1)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

Really love the lack of support Microsoft gives here when their program managers tell me to post here but haven't gotten any sort of response. Seeing that this issue is years old it just tells me PVA/Copilot Studio is just yet another piece of Microsoft vaporware that works only if you are a large enough company to get direct contact with engineering team.
jbonomo 44 on 08 Feb 2024 at 15:46:47

Like (1)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

I started to experience this recently too with no changes to any topics, just stopped working...before it stopped working it just went in a loop sending the same response over and over
AlexXks 16 on 07 Feb 2024 at 11:00:05

Like (0)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

Same error message on any topic after user input as `User's entire response`:
Env: Ms Teams. Error appears not for all users.

Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: InvalidDialogInterruption.
zafarshamsi 85 on 21 Jul 2023 at 06:46:42

Like (1)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

@renatoromao did you get any updates
zafarshamsi 85 on 21 Jul 2023 at 05:25:01

Like (0)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2030.

Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2030.
Kalok 8 on 13 Dec 2022 at 06:32:02

Like (0)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

I am also getting the same error 2001 after initializing the variable to the topic from Bot Framework Composer. without a variable, it's working with any error. But I need to get the value from the user in the adaptive card and use and store it in DB.
Community Power Pla... on 01 Jun 2022 at 09:52:41

Like (0)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

Still getting this error in 2022 without any fault in the topic. For me it happened running when adding a record to a table through a flow. The record was added correctly, the follow-up message displayed correctly and then Error 2001 popped up twice
DiegoPeres 327 on 27 Aug 2021 at 14:25:06

Like (0)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

Good, very good...
Community Power Pla... on 27 Aug 2021 at 14:22:20

Like (0)

Report

Re: Sorry, the bot can't talk for a while. It's something the bot's owner needs to address. Error code: 2001.

@Diego Sure, one of the Flows in my PVA just had stale connector connection. So it was failing. I had to re-connect it and flow worked so situation was resolved.