I am trying to run the graph sentiment bot sample , on running in the emulator I am getting the below error
UniversalBot("*") routing "hi" from "emulator"
Session.beginDialog(/)
Error: Dialog[*:/] not found.
Related
I just started getting 500 error.
I have a IOS pipeline that sends the info to Appcenter to distribute the app to test flight. Now getting error. No changes on my side.
##[error]{"code":"internal_server_error","message":"internal error (Support ID: c86b8112-a084-486c-9df8-a5ffc63fad81)"}
http response code: 500
Recently I was unable to publish my bot to Azure using publishing profile.
I was getting: TypeError - Cannot Read property 'AzureSubscriptionId' of undefined error.
The bot ran locally just fine.
The error was due to incorrect LUIS prediction resource specified in my publishing profile:
"luisResource":"xxxxxx"
I'm posting it here since the error message was really unhelpful and it took me a while to troubleshoot!
I created one normal echobot application and when i am trying to run it through the emulator locally it throwing the below error
Cannot post activity. Unauthorized.
plz help me out on this
Installed botium-cli
Installed botium-connector-alexa-smapi
Updated configuration file according to my skill
Was able to run emulator, was able to connect to my skill I have also recorded one conversation
Now I'm getting error
"UnhandledPromiseRejectionWarning: Error:
Skill simulation for simulation id
6720c6ce-e0c2-40ca-850e-fd0caaed1e3e failed with message: This
utterance did not resolve to any intent in your skill. Please invoke
your skill and try again with a different utterance or update your
interaction model to include this utterance before testing again"
What should I do to resolve this, I tied several utterances, tried invoking the skill on amazon developer console window. Nothing worked
Trying my hand at using Microsoft bot framework NodeJS and it seems to be giving me a -> POST Refresh access token failed with status code: 400 error when I try to run it in the botframework-emulator. Do any of you have a similar problem? Is this a bug with the framework itself or there is something I am missing?