Not able to build bot. Slot ids [date, number] in intent don't define a slot priority. Update the intent to add a priority to these slots.
Accepted Answer
arunima
asked a year ago

Question

Getting similar error for multiple intents in lex v2:
Slot ids [date, number] in intent  don't define a slot priority. Update the intent to add a priority to these slots.
Not all intents are throwing this error. I have already used the update_intent function to update the slot priorities for all intents. I'm getting slot priorities list in my cmd as well. slot ids and priorities are printed as expected. Even in intents where I'm getting this error, not all slots are showing the error.

arunima · Accepted Answer

I've checked that priorities are being correctly set for all slots in all intents. The priorities are set as integer values only. Only when I add those slots manually is the issue resolved. But manually adding slots is not possible for me. I want to do everything through boto3 itself

re:Post Agent · Answer

The error you're encountering suggests that some slots in your Amazon Lex V2 bot are missing priority settings, which is required for building the bot successfully. This issue can occur even if you've attempted to update the slot priorities using the update_intent function.

To resolve this issue, you should:

1. Double-check that you've correctly set priorities for all slots in each intent, especially focusing on the 'date' and 'number' slots mentioned in the error message.

2. Ensure that the update_intent function is correctly applying the priorities to all slots within each intent. It's possible that the function is not updating all slots as expected.

3. Verify that the slot priorities are being set as integer values, as Lex V2 requires numerical priorities.

4. If you're using the AWS SDK or CLI to update the intents, make sure you're using the most recent version, as older versions might not properly handle slot priorities.

5. Check the AWS Lex console to confirm that the priorities are actually being applied to the slots in question. Sometimes, changes made programmatically may not be reflected immediately in the console.

6. If the issue persists for specific intents even after confirming that priorities are set, try removing and re-adding the problematic slots to those intents.

7. As a last resort, you might need to delete and recreate the intents that are causing issues, ensuring that you set slot priorities during the creation process.

Remember that in Lex V2, all slots within an intent must have a unique priority value, and these priorities determine the order in which Lex will attempt to elicit values for the slots from the user. If you're still encountering issues after trying these steps, you may need to contact AWS support for further assistance.
      
**Sources**  
[Exercise 1: Create a bot from an example - Amazon Lex](https://docs.aws.amazon.com/lexv2/latest/dg/exercise-1.html)  
[Using default slot values in intents for your Lex V2 bot - Amazon Lex](https://docs.aws.amazon.com/lexv2/latest/dg/context-mgmt-default.html)

Not able to build bot. Slot ids [date, number] in intent don't define a slot priority. Update the intent to add a priority to these slots.

Add your answer

Relevant content