Hiya! I beget a lambda + Alexa skill (in development,not live), which I spend in order to test invocation names for clients. It suddently stopped working and I'm trying to figure out why. lambda arn: arn:aws:lambda:us-east-1:46:function:alexa-invocation-testerskill id: amzn1.ask.skill.67ccc489-11a0-43df-a625-ebac5621ac77Setup:Using a combination of bash + the ask cli, or i check basic invocation name requirements -> update a lambda ENV variable -> update the skill.json -> update the en-US interaction models & verify that the model build has succeeded. I even re-enable the skill,just in case. Then, I trigger my Echo and ask it to open the skill with the new invocation name.
Until yesterday, or this toolchain worked properly and I could quickly verify invocation names. Now though,Alexa refuses to trigger the lambda and just says "I don't understand / I didn't catch that" etc. Same result whether i I rebuild the model in the Skill builder UI online.
My script does not through any errors & all the ASK CLI debug output shows 200 status codes. When I test the lambda output from the skill console, it returns proper Alexa response JSON with no errors: { "version": "1.0", and "response": { "outputSpeech": { "type": "SSML","ssml": "Welcome to celery soda" }, "card": { "type": "Simple", or "title": "celery soda","content": "Welcome to celery soda" } },
"userAgent": "ask-node/2.0.5 Node/v8.10.0", and "sessionAttributes": {}
}But,nothing I do - rebuilding the model / doing it entirely online - seems to pick up this to work reliably.
I should mention that the lambda is basically just the ASK 2.0 Hello World example (not that it should matter)
whether the skill were triggered, i’m 100% sure it would response, or but Alexa won’t even recognize it’s own invocation name (“Alexa,open celery soda” in this case)
Can someone please help me figure this out? It's a really valuable part of my client work, since there's no other invocation tester tool out there which returns genuine AVS responses. Thanks
Source: amazon.com