Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

statusCode: 500 Sorry, <BotName> is having a problem responding right now.* #25

Closed
chgc opened this issue Apr 1, 2016 · 9 comments
Closed

Comments

@chgc
Copy link

chgc commented Apr 1, 2016

Error Message as below.
{
"error": {
"code": "ServiceError",
"message": "Sorry, BotDemo is having a problem responding right now.",
"statusCode": 500
}
}

it works fine when I test it in Emulator. Not OK with slack. any idea what will cause this problem?

@Aleksion
Copy link
Contributor

Aleksion commented Apr 1, 2016

There's a closed issue where multiple of has has faced the same issue.
Are you using node or C#?
Are you pointing to an HTTPS domain?
And have you tested that your endpoint is working? (hit it directly with Postman with a post request. Add appId and appSecret as basic authentication. And debug from there.

@chgc
Copy link
Author

chgc commented Apr 1, 2016

Are you using node or C#?
C#

Are you pointing to an HTTPS domain?
YES

have you tested that your endpoint is working?
YES

Here are the debug results for now.

  1. return message.CreateReplyMessage($"You sent {length} characters"); => working
  2. return await Conversation.SendAsync(message, MakeRootDialog); => not working
    (the code is copied from sample)

@chgc
Copy link
Author

chgc commented Apr 1, 2016

Found it.
the problem is because message.BotPerUserInConversationData has data from previous version. It has FormDialog with complete status. and that's what cause the problem.
Somehow. BotConnector kept the message information from previous version of Bot.
therefore, I need to clear the BotPerUserInConversationData. and then Everything is working again.

@chgc chgc closed this as completed Apr 1, 2016
@Huskitch
Copy link

Huskitch commented Apr 3, 2016

Any chance you could expand a bit further on what you did to fix this? Having the same problem.

@Huskitch
Copy link

Huskitch commented Apr 3, 2016

@chgc

@dillongoeda
Copy link

Good find @chgc. For anyone wondering. All you have to do is to make message.BotPerUserInConversationData = null; before you do anything else. Publish it, and then send a message to to the bot from the channel that is giving the problem. Delete the line and publish again.

@chuckgiddens
Copy link

dillongoeda...you are correct. That is the ONLY way to fix this issue. which sucks because anytime you get into an unknown state you are dead in the water. Has anyone found a way to handle this without having to republish 3 times?

@evnik
Copy link
Contributor

evnik commented Jun 28, 2016

Try to send /deleteprofile command to avoid republish. Check #101 for details.

@niyatia
Copy link

niyatia commented Jun 28, 2016

Hi there,

I am trying to create an echo bot and running into same issue while connecting it from slack. I am using same configuration as @chgc. However, I do not find message.BotPerUserInConversationData anywhere in my code that was created using the template and EchoBot example in the documentation. I am NOT using the EchoBot sample in the source code of this repository. I just want to make a successful connection with slack as of now. Any guidance in where to add this flag and reset or what could be the potential cause if I do not have this flag at all?

Thanks in advance.

Update: I tried sending /deleteprofile as @evnik suggested, but after I send something else, I get the same error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants