What is alexa error 701 (complete solution)?
When developing your 1st Alexa ability, problems will arise in areas that you just do not expect. For developers us square measure simply beginning out and attempting to check their first Hello World skill, you'll not be able to tell if the difficulty is along with your own code or if there is one thing missing in your configuration.
Luckily, several of the problems that new ability developers face boil all the way down to some easy mis configurations that square measure comparatively simple to resolve. Below, we have a tendency to define five of the foremost common problems that developers run into once testing their skills, using the take a look at machine with the developer console; the rationale why they occur; and the way to resolve the difficulty before submitting your ability for certification.
Now that you just have finished building out a rough ability and you wish to check it out, you'll take a look at it either in developer console or your Alexa device. after you invoke your ability by spoken communication your launch phrase, you may run into things delineated below.
You might additionally run into this error message whereas you're testing alternative intents, not simply Launch Request yet.
So, what will that error message mean? after you launched your ability, your ability sent back a response to Launch Request or another intent request; but, there was a problem with the response your ability sent back that caused the ability to finish the session. this suggests that the response JSON your ability sent back was un-happly.
[100% FIXED] Alexa error 701 (fixed)?
✅In order to require a better look into your response JSON, take care to log your response JSON to improve your ability to correct. This helps you to check what your ability is causation back. If you're exploitation an AWS Lambda function as your skill's backend, creating use of check event may facilitate.
✅Depending on the SSL certificate that your custom internet service is exploitation, you may need to pick out the relevant setting at intervals your end point. check that that your end point complies with the necessity listed in Host a Custom ability as an online Service.
✅You will check the profile that you just area unit presently exploitation for the device by asking “Alexa, that account is this?”. If the account mentioned isn't the developer account that you just area unit exploitation to make your ability, you'll then switch profile to the one that has your ability enabled by spoken communication “Switch accounts”.
✅Use the Utterance Profiler in the developer console to check the various utterances that don't seem to be operating by examining however your utterances area unit being mapped to your outlined intents. this can allow you to see what intents Alexa is attempting to map your vocalisation to. it'll additionally offer you a concept of that utterances area unit operating higher for your ability, yet as that utterances don't seem to be properly getting into the intents.
✅Browser problems
✍️Use Chrome/Firefox for testing
✍️Disable any extensions or plugins you'll have put in
✍️Run your browser in private/incognito modes
✍️Clear your browser cache
✍️Local surroundings problems
✍️Check your antivirus software package and firewalls that would probably block the check machine and ports accessed by your browser.
✍️Check your native network settings that would probably block the check machine and ports accessed by your browser
✍️Update your device country settings.
Click here to visit official website
CONCLUSION:-
Now that you just have find out about five of the foremost common error responses that Alexa provides and of what they mean, hopefully debugging your ability is way easier to handle. If you have got any queries on your ability building journey, you'll post queries and sit down with alternative fellow Alexa ability builders on our developer forum.
EmoticonEmoticon