This is pretty strange situation, so hear me out. Before I go further, also know, that this problem I am about to describe, just started happening. This was all working before about 3 days ago.
I have two intents that both use the AMAZON.NUMBER slot type. One is passing in a dollar amount "Transfer 1200 dollars" and one is passing in a one time password "Verify my one time password 12345" The slot names are different, however, they are both set to that AMAZON.NUMBER type. When using the testing tool in the dev console, that one time password intent stopped passing in the value. When I check logs of the lambda code, it's saying that it is receiving "undefined". Or actually, just not receivig the value from the intent, so the const I set in code is set to "undefined" However, when I test the funds transfer intent, it works fine. So that is really interesting. NOW, here is the most interesting part. If I invoke this skill through my actual Alexa dot using my voice, both work fine. ???? The skill is not published yet. However, others in my organization will eventually need to work on this and test it. So I am not wanting to share with them until I can figure this out.
And I repeat, this used to work fine in both the test console and the dot. Now, only the funds transfer works with test console, and both will work if actually tested via voice.
Anyone see anything like this before? I am fairly new to this, but I did search the forums before posting. I cannot use the AMAZON.FOUR_DIGIT_NUMBER type as my OTP is 5 digits long, I can't make it shorter. Thanks for reading, and offering any advice that you may have to debug.