Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

AWS Lex seems to be broken for specific slots like Amazon.EmailAddress and Amazon.US_FIRST_NAME

0

This is started happening few hours ago, it was working fine and suddenly stopped working, Amazon.EmailAddress is not working at all. Its on region=us-west-2 and on LexV1

For Amazon.EmailAddress => none of the email addresses are detected

Also for Amazon.US_FIRST_NAME behaviour is strange, John => not detected as first name Jonathan => working fine

Topics
Machine Learning & AI
Tags
Amazon Lex
Language
English
asked 3 years ago617 views
4 Answers
0

Thanks for reaching out.

We are looking into this issue, Can you please provide the answer of the below questions for us to debug further

  • Is it only for Lex V1 ?
  • Is the bot using advance option = false ?
  • Is it in first turn or slot elicitation turn ?
  • Can you please DM us with your AccountId, BotId and few requestIds or reach out through AWS customer support for us to debug further ?

Thanks Tania

answered 3 years ago
  • rePost-User-7146884
    3 years ago

    Is it only for Lex V1 ? => Yes I think and also i tried same intent on another v1 bot and its working fine, looks like issue is bot specific.

    Is the bot using advance option = false ? => No, Advanced option is enabled

    is it in first turn or slot elicitation turn ? => First turn only

    Regarding DM I'm not sure how to DM details,

    Thanks for your help.

0

Thanks for getting back to us.

  • Can you also confirm if you have configured a dialogue or fulfillment lambda?
  • Are you facing issues for audio inputs or text inputs or both?
  • Can you please open a customer case with us with the accountId, botId, requestId details for us to help you further?
answered 3 years ago
  • rePost-User-7146884
    3 years ago

    I tried by creating new bot of v1 and i thought i'll copy all my intents over there, but this issue started coming again, i only have one intent with slot which accepts email and nothing else,

    Can you also confirm if you have configured a dialogue or fulfillment lambda? => No it just returns parameters.

    Are you facing issues for audio inputs or text inputs or both? => facing issue for both.

    Can you please open a customer case with us with the accountId, botId, requestId details for us to help you further? => Actually its a paid service so we cannot afford.

    RequestID: 325e2728-d075-43a8-92c7-eb2480f535c7

0

Checked the above requestId. Seems like the Advanced options are disabled for this bot. Can you please rebuild the bot with it enabled and try again? This blog for best practices on bot building can also support you in building a bot that will work well for your use case. - https://aws.amazon.com/blogs/machine-learning/best-practices-for-creating-amazon-lex-interaction-models/ Hope this helps.

answered 3 years ago
0

We further looked into the issue and identified an issue in our system which is not honoring the advanced options. We are actively working on a fix. Thank you for your patience while we remediate this.

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content