# RASA 2.0 Stories do not continue after form is handled

**URL:** <https://forum.rasa.com/t/rasa-2-0-stories-do-not-continue-after-form-is-handled/36381>\
**Category:** Rasa Open Source\
**Created:** [October 28, 2020, 4:53pm UTC](https://forum.rasa.com/t/rasa-2-0-stories-do-not-continue-after-form-is-handled/36381 "2020-10-28T16:53:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fabrice-toussaint](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/fabrice-toussaint/32/11162_2.png) [@fabrice-toussaint](https://forum.rasa.com/u/fabrice-toussaint)\
**Post date:** [October 28, 2020, 4:53pm UTC](https://forum.rasa.com/t/rasa-2-0-stories-do-not-continue-after-form-is-handled/36381/1 "2020-10-28T16:53:50Z")

</div>

Hello RASA heroes,

I migrated my forms from RASA 1.X to RASA 2.0 and they are working now (YEAH!). However, now my stories do not continue properly after. An example story can be seen below:

```
steps:
  - intent: intent1
  - action: action1
  - action: action2
  - action: form
  - active_loop: form
  - slot_was_set:
    - requested_slot: slot1
  - slot_was_set:
    - slot1: 12AB
  - slot_was_set:
    - slot1: 12AB
  - slot_was_set:
    - requested_slot: slot2
  - slot_was_set:
    - slot2: 3SX
  - active_loop: null
  - slot_was_set:
    - requested_slot: null
  - action: action3
  - intent: affirm
  - action: utter_confirm

```

Everything works fine up until and including action3. However, when I then type “Yes” (this is recognized as affirm intent with a 99% probability) the bot just goes to the next line instead of uttering.

Any ideas on why this is happening? I thank you in advance!

---

<div class="post-metadata">

**Author:** ![Johan1us](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/johan1us/32/14245_2.png) [@Johan1us](https://forum.rasa.com/u/Johan1us)\
**Post date:** [October 28, 2020, 5:28pm UTC](https://forum.rasa.com/t/rasa-2-0-stories-do-not-continue-after-form-is-handled/36381/2 "2020-10-28T17:28:17Z")

</div>

Hi @fabrice-toussaint

Your story looks good to me. You would expect that after `affirm` the bot uses `utter_confirm`.

You can check if there is something in `rules.yml` or a different story that might confuse the bot.

What do you get back if you run the bot in the terminal with `rasa shell --debug`?

---

<div class="post-metadata">

**Author:** ![fabrice-toussaint](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/fabrice-toussaint/32/11162_2.png) [@fabrice-toussaint](https://forum.rasa.com/u/fabrice-toussaint)\
**Post date:** [October 29, 2020, 8:44am UTC](https://forum.rasa.com/t/rasa-2-0-stories-do-not-continue-after-form-is-handled/36381/3 "2020-10-29T08:44:19Z")

</div>

Apparently it predicts action\_listen instead of continuing the story. Do you have any idea why this happens?

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/rasa/original/2X/0/06639087b6159f5c371c4dfb231791adabb296f3.png)

EDIT: I think it might have something to do with max\_history of Memoization Policy.

---

<div class="post-metadata">

**Author:** ![Johan1us](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/johan1us/32/14245_2.png) [@Johan1us](https://forum.rasa.com/u/Johan1us)\
**Post date:** [October 29, 2020, 9:57am UTC](https://forum.rasa.com/t/rasa-2-0-stories-do-not-continue-after-form-is-handled/36381/4 "2020-10-29T09:57:26Z")

</div>

Hi @fabrice-toussaint

I see at the first line: `rasa.core.policies.rule_policy - There is no applicable rule.`

Did you activate the `RulePolicy` in `config.yml`?

For example like this in `config.yml`:

```
policies:
   - name: MemoizationPolicy
   - name: RulePolicy
   - name: TEDPolicy
     max_history: 5
     epochs: 100

```

If after `- action: action3 ` followed by `- intent: affirm ` always `- action: utter_confirm ` must be used by the bot, you can include this in `rules.yml`.

For example like this in `rules.yml`:

```
- rule: Use after action3 + affirm always -> utter_confirm
  steps:
  - action: action3
  - intent: affirm
  - action: utter_confirm

```

You can also do this in `stories.yml`. I always use the following principle: If the bot has to do it in 100% of the cases, I include it in rules.yml. If it is an exception, I include it in `stories.yml`.

See the documentation:

> **[Policies](https://rasa.com/docs/rasa/policies/)**

> **[Rules](https://rasa.com/docs/rasa/rules/)**
>
> Use Rasa rules to respond to FAQs, fill forms, or handle fallbacks gracefully.

> **[Stories](https://rasa.com/docs/rasa/stories/)**
>
> Stories are used to teach Rasa real conversation designs to learn from providing the basis for a scalable machine learning dialogue management.

Does this suggestion work for you?

---

<div class="post-metadata">

**Author:** ![fabrice-toussaint](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/fabrice-toussaint/32/11162_2.png) [@fabrice-toussaint](https://forum.rasa.com/u/fabrice-toussaint)\
**Post date:** [October 29, 2020, 10:02am UTC](https://forum.rasa.com/t/rasa-2-0-stories-do-not-continue-after-form-is-handled/36381/5 "2020-10-29T10:02:09Z")

</div>

Thank you again @Johan1us, this is very helpful and I will implement it! I do have the policies included as you mentioned (the RulePolicy was activated). When I increased my max\_history it worked fine but I am going to change it as you mentioned by including it in the rules.yml!