I have a checkpoint that I’d like to restrict via slot_was_set so it only gets triggered when a user has a value in a specific slot. Here’s how I’ve set that up:
- story: battle steps: - checkpoint: battle_started slot_was_set: - battle_id - intent: Battle Fallback - slot_was_set: - battle_id - action: my_custom_action
But… This throws the following error when I run
rasa data validate:
Checkpoint 'battle_started' has an invalid slot: ['battle_id'] Items under the 'slot_was_set' key must be YAML dictionaries. The checkpoint will be skipped. More info at https://rasa.com/docs/rasa/stories
Based on the message, I assume it’s because it’s expecting a key/value pair there, but I don’t want to provide a specific value for it so that it behaves the same way as an intent-specific slot_was_set rule (i.e. when I don’t provide a value, it’s evaluated as being either set or not set)
Does the checkpoint-specific slot_was_set work differently than the intent-specific one? Am I unable to use it in the “set or not set” way that I’m looking to?