1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi Aaron,
In your case, the best path forward is to delete the impacted intent and recreate a new intent with same settings. Also, we have deployed a fix to console and this problem should not occur again.
Sorry about the churn and we hope this unblocks your development.
Contenus pertinents
- demandé il y a 5 mois
- demandé il y a un an
- demandé il y a un mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 3 mois
I think this note may have something to do with the situation.
Note On August 17, 2022, Amazon Lex V2 released a change to the way conversations are managed with the user. This change gives you more control over the path that the user takes through the conversation. For more information, see Understanding conversation flow management (p. 18). Bots created before August 17, 2022 do not support dialog code hook messages, setting values, configuring next steps, and adding conditions.