Alright, this one’s annoying. When you test in the Storyline browser, the skill will just stop, or in the developer console tester or on an Alexa device, it’ll say: ‘there was a problem with the requested skill’s response’. There are multiple causes, so let’s work out what is the cause of your one.


  • Error occurs after a user reply before audio plays, or before audio plays in a block.
    • This most likely means that your audio URL is incorrect or the file type is incompatible.
    • Check this article to make sure your links match the example and that you have converted your audio file.
  • Error occurs after a user reply
    • This is a Storyline bug. Let’s use a fix.
    • First, disconnect the user reply from the block it connects to. For example, if my user reply of ‘yes’ connects to ‘Block A’, disconnect ‘yes’ from ‘block A’ and make it connect to no blocks or just another block.
    • Then, upload to Alexa. After, reconnect ‘yes’ and ‘Block A’, and upload to Alexa again.
  • Error occurs before Alexa says something containing an SSML tag
    • Lots of people can accidentally make typos on this one.
    • NEVER copy from a word processor or even this site. Type it out manually. Always use this apostrophe: ‘ – instead of the ” symbol. If you copy the ” symbol, it could become a curly ” which would mean the SSML tag doesn’t work. Just replace “s with ‘s. Check you’re only using ‘ symbols.
    • Make sure your SSML tag is formatted correctly. Follow THIS guide by Amazon to make sure everything matches.
  • Error occurs before API request
    • This means there’s an issue with the API request.
    • Above is what a simple API request from a Google Spreadsheet should look like. The URL to the JSON file should be in the box which is highlighted blue.
    • For most API requests, leave the ‘Headers’ box blank. Your variable request should ALWAYS go in the bottom box. If your spreadsheet only has one cell with data in it, the request will be ‘data=api_response.feed.entry.0.title.$t;’ because computers count from 0, not 1.
    • Common mistakes include accidentally changing ‘GET’ to ‘POST’ and including ‘{variable}’ instead of just ‘variable’ in the API request.
    • Make sure your spreadsheet’s values begin in Cell A2 instead of A1. A2 will correspond with 0, A3 with 1, A4 with 2, etc.
    • If you still can’t fix it, start from scratch with THIS article.
Categories: Bug Fixes

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.