lex latest version not displayed in slack

0
  1. I have created a lex bot and integrated with Slack.
  2. changed few slots in lex, saved the intent, build it and published it.
  3. When i check it from slack, i am still getting the older version of lex.
  4. How to solve this?
asked a year ago233 views
1 Answer
0

Hello,

  • Generally speaking, this scenario can occur when sending a postText call, then update botAlias, then sending another postText using the same session (session did not expire yet) as the first postText call. Then, the second postText call will point to the version before making putBotAlias call.

  • This is an expected behavior, because a user can't have two independent conversations with two different versions of the same bot.

https://docs.aws.amazon.com/lex/latest/dg/API_runtime_PostText.html

A user can't have two independent conversations with two different versions of the same bot. For example, a user can't have a conversation with the PROD and BETA versions of the same bot. If you anticipate that a user will need to have conversation with two different versions, for example, while testing, include the bot alias in the user ID to separate the two conversations.

Note:- Please note that when we create an alias for the specified version of the bot or replace an alias for the specified bot(even from console), a “PutBotAlias” API call[1] is logged in the CloudTrail event history.



  • The only way session information can be removed is either to wait for the session timeout limit[2] to breach, or by making the DeleteSession API [3] call.

  • Amazon Lex retains context information—slot data and session attributes—until a conversation session ends. To control how long a session lasts for a bot, we set the session timeout. By default, session duration is 5 minutes, but we can specify any duration between 0 and 1,440 minutes (24 hours). Apart from that, DeleteSession API call would remove session information for a specified bot, alias, and user ID.



In your specific case, I would request you to please create a support case with our team for investigating the API calls that are being made from your account to confirm the returned version response/behavior.

Please do not post any sensitive information over re:Post since this is a public platform.



References:

[1] PutBotAlias - https://docs.aws.amazon.com/lex/latest/dg/API_PutBotAlias.html

[2] Setting the Session Timeout - https://docs.aws.amazon.com/lex/latest/dg/context-mgmt-session-timeout.html

[3] DeleteSession - https://docs.aws.amazon.com/lex/latest/dg/API_runtime_DeleteSession.html

profile pictureAWS
SUPPORT ENGINEER
Yash_C
answered a year 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.

Guidelines for Answering Questions