This issue is occurring for the Java ASK SDK v2.3.1.
Background info: I have three built-in intents that trigger the end of a session: AMAZON.StopIntent, AMAZON.CancelIntent, and AMAZON.NoIntent. According to all the documentation that I could find regarding the utterance "exit", this utterance is handled by the device firmware rather than any of the built-in intents.
Bug: After the utterance "exit" at any point throughout the app, a "Unable to find a suitable request handler" error appears on the skill's lambda logs. From a user perspective, the session ends appropriately, but the error is triggering our CloudWatch alarms.
Is there any way to handle this error in the context of the skill or the Lambda function? Seeing as "exit" is seemingly handled by the device and not any of the handlers, I'm unsure how this error might be occurring (unless there is an issue with the Java SDK v2).