# From action never ask to fill slot if it is already filled

**URL:** <https://forum.rasa.com/t/from-action-never-ask-to-fill-slot-if-it-is-already-filled/4708>\
**Category:** Rasa Open Source\
**Created:** [January 28, 2019, 10:41am UTC](https://forum.rasa.com/t/from-action-never-ask-to-fill-slot-if-it-is-already-filled/4708 "2019-01-28T10:41:05Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![smn-snkl](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/smn-snkl/32/902_2.png) [@smn-snkl](https://forum.rasa.com/u/smn-snkl)\
**Post date:** [February 14, 2019, 8:25am UTC](https://forum.rasa.com/t/from-action-never-ask-to-fill-slot-if-it-is-already-filled/4708/17 "2019-02-14T08:25:29Z")

</div>

In case somebody is suffering from the issues discussed here and applying the “solution” mentioned above, I want to note that this solution is not 100% safe either.

Resetting slots in the `submit` method doesn’t prevent forms being filled automatically without asking for user input in situations like this:

```auto
* user_likes{"item": "strawberries"} # "I like strawberries"
  - utter_user_likes
* order_food
  - form_food
  - form{"name": "food"}
  - form{"name": null}

```

Where the user will not be asked for the slot `item` again, just because an entity matching the slot was mentioned somewhere in the conversation before.

Discussing this [here](http://forum.rasa.com/t/should-slots-generally-be-reset-to-none-after-action-is-executed/4737/4)

---

_[View the full topic](https://forum.rasa.com/t/from-action-never-ask-to-fill-slot-if-it-is-already-filled/4708)._
