I've been seeing some really strange behaviors lately with custom Alexa skills. With certain user responses (primarily short ones), the skill will abort without sending a request to the fulfillment endpoint. For prompts that have a reprompt in the response body, instead of ending the session, it just says the reprompt in response to the user. This issue is even more clear when using Dialog.UpdateDynamicEntities directives. Here's an example dialog:
> Launch Request
Simulator/Device: Hello! Say a color like red, green, or blue
> endSession = false
> Dialog.UpdateDynamicEntities adds "red", "green", "blue", "redish", "ocean", and a couple others as REPLACE values for DynamicColorSlot
> no reprompt
Simulator/Device: <Audio only response>
> no request sent to lambda/endpoint
The intent looks something like this:
If I return a reprompt with the LaunchRequest response, instead of getting <Audio only response> I get the reprompt message.
Note: this happens even without using dynamic slot values. Whether it matches an intent or not, it does not send a fallback intent or a matched intent. Just bombs. This also started happening to skills that worked previously.
Whatever guidance you have to work around this would be great. Anyone else seeing this?
Director and Principal Architect