There are a few users that receive a message back from Alexa along the lines of "Sorry, I couldn't reach ..." or "I can't communicate with ... "
These users claim that when they relink their accounts to our service, it works - for a little while. They eventually run into the same problem. Where is this failing?
When a user speaks to Alexa, it should reach out to my lambda function, which in turn communicates with our server-side code. Does this error mean that Alexa can't reach our lambda function? If so, that would mean that their Alexa account doesn't have our skill enabled, right? Or is this an error that is stated based on a response our lambda function responds with - if so, what is the error name?