All of sudden I am getting the above error where ever i use Slot Types.Its started just few hours back.
I dont know what happened suddenly , I haven't changed any thing in Alexa interaction model.
I have demo of skill in few hours.please help.Its very urgent.
Hi,
Can you please provide more details regarding the structure of your interaction model?
We recently made new tools available to help with the creation and testing of skills. The new features inadvertently impacted a small number of skills. We fixed the issue yesterday and all live skills should work as expected. Please post here if you have any more issues and we will monitor and provide assistance. For skills in development, you can now resolve this issue by clicking ‘Save’ on the interaction model tab or by clicking Build Model in Skill Builder (beta). We apologize for the inconvenience.
There were 2 things that may have caused this to keep happening for me:
Hi, our skill is experiencing the same issue. When we say: "Alexa, launch n wave". Then Alexa would say: "Sorry, I am having trouble accessing your enwave skill right now.". But when we use the skill with other utterances. It is working.
Hi,
We are aware of the issues that have been reported on this thread and are continuing to work on a fix. We will post here again when we have more information to share.
I have been receiving this error. I am using the FactsTemplate. I added my appID and I get this error. When I used this template as is without my appID, I got an expected connection error from the Response side. Is there any update to the status of the fix?
Any update here? This is impacting our company's sponsorship at a major developer convention.
Everyone try to resave your interaction model. I returned to the standard over beta and resaved mine and everything is working now... resubmitted for certification now and crossing my fingers. good luck everyone.
Just tried mine again and it is still failing with the same error. @NickG@Amazon any update on the process of a fix for this error/is there a work around that we can use as an intermediate step so we can make our skills work?
This is happening for me as well. Is there any way to escalate this or to find out how long it's going to take to have resolution? Does Amazon have a posted schedule of when they do system upgrades -- it'd be nice to have visibility on that so I can have a sense of when things could be destablized like this.
I have the same issue.
It is very frustrating that nobody answers, I'm trying to fix this issue for 2 days now. I've worked all weekend because monday I have to present this...useless
It's outrageous that we don't get any answer.
Is this still an issue? Utterance capitalization seems to be affecting whether the response is generated correctly or not at the moment....
I'm using a very simple schema:
{
"intents": [
{
"intent": "AMAZON.HelpIntent"
},
{
"intent": "AMAZON.StopIntent"
},
{
"intent": "AMAZON.CancelIntent"
},
{
"intent": "RefineSessionYes"
},
{
"intent": "RefineSessionNo"
}
]
}
The utterance is as follows:
RefineSessionYes yes RefineSessionNo no
When testing the skill, if I type in a capital "Yes", then it works. If I type in lower case, then it doesn't work. Yes =
{
"session": {
"sessionId": "SessionId.408acbdb-c819-4c05-8a3b-d66aa916c4d5",
"application": {
"applicationId": "xxxxxx"
},
"attributes": {},
"user": {
"userId": "xxxxxxxx"
},
"new": true
},
"request": {
"type": "IntentRequest",
"requestId": "EdwRequestId.224b6463-f82e-40bd-b12d-6146cf1f5f3e",
"locale": "en-US",
"timestamp": "2017-04-22T02:04:52Z",
"intent": {
"name": "RefineSessionYes",
"slots": {}
}
},
"version": "1.0"
}
yes =
Unable to generate request for your skill.
Are you still having the same issues? It's crazy that it's been over 24 hours and no one has responded yet. I would think that "yes" or "no" responses would be fairly common
After a suggestion from another user, I changed to AMAZON.YesIntent and AMAZON.NoIntent . After changing, things seem to be working
For what it's worth, I'm experiencing the same thing. Created a simple app that will repeat back to the user colors that are spoken. Created a custom slot containing colors. Works fine when uttering "tell me about red", but will get the error stated above when just uttering "red". Tried AMAZON.Color type just to see if behavior changed and it did not.
Looks to be some sort of parsing error when the Service Simulator attempts to generate the request. The one word utterance was working the last time I checked which was probably a week ago.
same here for many intents whiche have been working 2 days ago... looks a little bit like the latest changes been more like a downgrade :(
simple intents like
show actionmovies stopped working completely
skillid: amzn1.ask.skill.12e654d1-aafd-4668-be72-3b8715e4e183
If this is impacting you, please provide a skillid for whatever model it's failing to generate a request for.
@Brian@Amazon where could we find this "Skill-Id"? I think there is no attribute "Skill-Id" on Alexa-Skills available.
In the developer portal, go to 'Skill Information'. There you will see the 'Application ID'. I believe that is the Skill ID.
Mine isn't working. Here is my skill id. It was working fine yesterday. Now getting the "Unable to generate request for this skill" error.
amzn1.ask.skill.bf5919cb-61a4-48e8-8611-b33fe92f549e
amzn1.ask.skill.c9980f89-8a8c-4193-a07c-007985cea9a3
Mine was working earlier today, I have been doing a lot of testing within the past few hours. I ended up commenting out most of my skill's functionality to just return what the user's input is, however this even returns the error: "Unable to generate request for your skill."
Here's mine:
amzn1.ask.skill.89fcc20f-c396-4ce6-b4f1-e82c04596436
Was working prior to this week. Sample utterances are below - anything with a single slot and no text is failing, two slots work fine.
These are failing:
WelcomeIntent {Option}
AcademicProgramIntent {Program}
AcademicProgramIntent {Major}
FoodIntent {FoodType}
These intents/utterances work fine:
WelcomeIntent find {Option}
AcademicProgramIntent i like {Program}
AcademicProgramIntent i am interested in {Major}
FoodIntent can i eat {FoodType}
Hi,
My skill was working fine until I tried to submit it as private skill using CLI. I added "distributionMode": "PRIVATE" line in downloaded skill manifest file and updated skill. Then it started giving me an issue in the simulator "Unable to generate request for your skill.". Please help.
Thanks!
For anyone who may be struggling with this, after some tinkering I found a way that worked for me. I found that having "required" slots was causing the issue. As soon as I set the slots as not required and managed the dialog logic in my intent rather than letting the skill builder manage it, it worked.
25 People are following this question.
