The remote endpoint could not be called, or the response it returned was invalid. about skill-sample-nodejs-fact

[melrom]

Hi - I was getting this error but it was because the name that I gave my intent in the skills builder did not match the js example for lambda. Namely, GetNewFactIntent -- you must name the intent in the skills builder to be exactly the same (or alternatively, change this line in the lambda code example [currently, it's line 112]). Just figured I would add this since I was getting the same error in case it helps someone else.

[lawardy]

In Lambda, check timeout value (basic setting >> timeout).

When I used default 3 secs, I got the same error. When I changed to 30 secs, it works.

Maybe it need more time to load the 1st time or 3 secs is just not enough.

[alephnode]

I'm working through this tutorial tonight and can confirm that I'm getting the same error on the testing section.

[alephnode]

Looks like tonight (06/22/2017) the N. Virginia center is experiencing issues with Lambda services:

https://status.aws.amazon.com/

Error message: 6:26 PM PDT We are investigating increased error rates for Lambda integrations and Custom Authorizers in the US-EAST-1 Region.

I just tried a separate tutorial (https://github.com/alexa/skill-sample-nodejs-howto) and selected the Ireland service center and passed the testing phase.

[LinusSkucas]

Thanks, should of checked there.

[swapnilsaykar]

I am still facing the same issue in both N. Virginia and Ireland

[LinusSkucas]

Are you sure? I just checked status.aws.amazon.com and it looked all right.

[swapnilsaykar]

Yup - I am sure. This is the error I am getting as per my cloudwatch logs:

2017-06-25T17:21:41.029Z c0c17851-59ca-11e7-b02a-b1b3a688e889
{
"errorMessage": "No 'Unhandled' function defined for event: Unhandled",
"errorType": "Error",
"stackTrace": [
"AlexaRequestEmitter.EmitEvent (/var/task/node_modules/alexa-sdk/lib/alexa.js:194:15)",
"AlexaRequestEmitter.ValidateRequest (/var/task/node_modules/alexa-sdk/lib/alexa.js:160:23)",
"HandleLambdaEvent.i18n.use.init (/var/task/node_modules/alexa-sdk/lib/alexa.js:113:29)",
"/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:190:9",
"done (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:281:21)",
"/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:302:7",
"I18n.loadResources (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:238:7)",
"I18n.changeLanguage (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:301:10)",
"load (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:186:14)",
"I18n.init (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:195:7)"
]
}

[swapnilsaykar]

I tried adding sessions handler as suggested in this:
amazon-archives/skill-sample-nodejs-calendar-reader#6

var newSessionHandlers = {
'LaunchRequest': function () {
this.handler.state = states.SEARCHMODE;
this.emit(':ask', skillName + " " + welcomeMessage, welcomeMessage);
},
'Unhandled': function () {
this.emit(':ask', HelpMessage, HelpMessage);
}
};

But still getting the same error

[LinusSkucas]

In the developer console go to the testing page for your skill and follow the instructions to test it. When you click ask [your skill name] does it return The remote endpoint could not be called, or the response it returned was invalid.?

[swapnilsaykar]

Yes - that is what is returns. In the developer console I am going to the testing page for the skill and then following the instructions.

I am getting the error - The remote endpoint could not be called, or the response it returned was invalid.

[gautamdevkhanna]

Same for me as well...

[trinipeng]

I am getting the same error.

[LinusSkucas]

Check what the skill is returning. If something is off in the response, then Alexa won't like it. Test the skills response in the AWS console.

[AITB]

I'm having this issue too. The solutionby @lawardy didn't solve my issue.
I am getting this issue from following both the fact and trivia skill tutorials. I have followed these before and having workings skills for both of these. My recent skills, following the same tutorials, all show this error. I have also tried to change the default endpoint of my broken skills to one of the skills that does work's lambda but it still shows the same issue. Which is why I don't think the issue is with the aws lambda part.

[LinusSkucas]

I've given up on using this and have switched entirely to flask-ask. This is far the best (in my opinion) sdk.

[ConorMatthews]

That worked for me!
Thanks so much!

[nstajduhar]

@ConorMatthews How did you fix this??

[ConorMatthews]

@nstajduhar I followed @melrom instructions because it was calling an intent list that was not there because when setting the intents up i did not follow the instructions advice to call it GetNewFactIntent, but called it otherwise. In the code it tries to call GetNewFactIntent however it was not named that so you need to go into your code and change GetNewFactIntent to whatever you called your intent list.
Hope this helps

[nstajduhar]

@ConorMatthews where is this GetNewFactIntent? I have no clue where to find that

[ConorMatthews]

@nstajduhar if you go to the example code where you changed the facts, on line 112 there should be the code, just change that.
Alternatively change your intent lists name to GetNewFactIntent

[nstajduhar]

@ConorMatthews facts? I didn't come across that? Can you link a screenshot

[ConorMatthews]

Are you using https://developer.amazon.com/alexa-skills-kit/tutorials/fact-skill-1 as a starting point?
If not try it

[ConorMatthews]

That is a tutorial made by amazon

[nstajduhar]

I have done all this but I don't see anywhere with a line number 112

[nstajduhar]

@ConorMatthews nvm I got it now thanks!

[naik899]

@ConorMatthews How did it get fixed. Can you help me with this?

[soundarsurya]

can anyone help me to fix the same problem for mt code...????
i have planned to make an automation so when it call form skill it gives the same error....

[naik899]

@soundarsurya I got it fixed by making my api response faster.

[soundarsurya]

@naik899 could you explain in detail please...??

[Juresse]

The remote endpoint could not be called, or the response it returned was invalid.

[naik899]

@soundarsurya @Juresse This error can be for couple of reasons as per my experience with Alexa skill set

1. Once it was because the name that I gave my intent in the skills builder did not match the js example for lambda
2. In Lambda, check timeout value (basic setting -> timeout). When I changed to 10 secs, it works.

[soundarsurya]

@naik899 thanks for the response.
i have changed the execution time but i am getting the same?
have any other way to fix??
?

[dm-grinko]

Guys, you should increase time and use HTTPS instead of HTTP. Hope it helps someone.

[soundarsurya]

I have increased the execution time but seems to be the same error. then i leave that and choose HTTP option instead AWS lamba.

…

On Wed, Apr 11, 2018 at 3:51 PM, Dmitry Grinko ***@***.***> wrote: Guys, you should increase time and use HTTPS instead HTTP. Hope it helps someone. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ahe8vNCNE4jQ2csOaT_6qsuY3Su5flvUks5tndlCgaJpZM4ODENV> .

[franklin-lobb]

@soundarsurya Are you still experiencing a problem? I took a look at the history and I'm not sure what you're experiencing. I have not seen this (unmodified) sample hit the timeout threshold, so I would lean towards something else. However, since this sample has been updated, you have a few options - start over with the latest code which uses the new version of the SDK, use the Serverless Application Repository in AWS Lambda to create the skill backend code, or continue troubleshooting this. LMK what you prefer.

[soundarsurya]

What I'm experiencing problem is: when I call from Alexa skill test it shows "the remote endpoint could not be called". I have checked and changed execution time of code but still I'm getting the same.

…

On May 3, 2018 4:47 PM, "franklin-lobb" ***@***.***> wrote: @soundarsurya <https://github.com/soundarsurya> Are you still experiencing a problem? I took a look at the history and I'm not sure what you're experiencing. I have not seen this (unmodified) sample hit the timeout threshold, so I would lean towards something else. However, since this sample has been updated, you have a few options - start over with the latest code which uses the new version of the SDK, use the Serverless Application Repository in AWS Lambda to create the skill backend code, or continue troubleshooting this. LMK what you prefer. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ahe8vAYII9xmoqtKEBSDtqtNiggMaUHVks5tuuc0gaJpZM4ODENV> .

[franklin-lobb]

Is the endpoint a Lambda function or an SSL endpoint? If it's a Lambda endpoint, I would check to confirm the full arn is present and correct in the skill endpoint configuration (with no extra spaces), the Lambda function has the Alexa Skill Kit trigger and the Skill ID verification in the trigger is either not enabled, or is set to the correct skill id.

More info on endpoint: https://developer.amazon.com/docs/devconsole/build-your-skill.html#custom-model
More Info on Lambda hosting: https://developer.amazon.com/docs/custom-skills/host-a-custom-skill-as-an-aws-lambda-function.html

[franklin-lobb]

@soundarsurya are you still experiencing this? If so, can you add some detail about your configuration? http endpoint or Lambda? if http, what kind of certificate are you using? Do your server logs show any sort of activity? If Lambda, does Alexa have permission to invoke your Lambda function? Are there any entries at all in the CloudWatch log?

[chfw]

please follow the youtube video here to get over the lambda connection issue: https://www.youtube.com/watch?v=QkbXjknPoXc

[franklin-lobb]

closing due to age