# Execution Error for Form Action after migrating from Rasa 2.8.0 to 3.6.13

**URL:** <https://forum.rasa.com/t/execution-error-for-form-action-after-migrating-from-rasa-2-8-0-to-3-6-13/61161>\
**Category:** Rasa Open Source\
**Created:** [February 27, 2024, 8:30pm UTC](https://forum.rasa.com/t/execution-error-for-form-action-after-migrating-from-rasa-2-8-0-to-3-6-13/61161 "2024-02-27T20:30:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![steve1](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@steve1](https://forum.rasa.com/u/steve1)\
**Post date:** [February 27, 2024, 8:30pm UTC](https://forum.rasa.com/t/execution-error-for-form-action-after-migrating-from-rasa-2-8-0-to-3-6-13/61161/1 "2024-02-27T20:30:05Z")

</div>

After migrating from Rasa 2.8.0 to 3.6.13, we are having issues with a custom form action in our bots. When I run the action to query a Jira board for a ticket, with the ticket ID as the input, I get the below error:

```auto
rasa.engine.graph - Node 'select_prediction' running 'DefaultPolicyPredictionEnsemble.combine_predictions_from_kwargs'.
rasa.core.policies.ensemble - Execution of 'query_jira_form' was rejected. Setting its confidence to 0.0 in all predictions.
rasa.core.policies.ensemble - Made prediction using user intent.
rasa.core.policies.ensemble - Added `DefinePrevUserUtterFeaturization(False)` event.
rasa.core.policies.ensemble - Predicted next action using TEDPolicy.
rasa.core.processor - Predicted next action 'utter_goodbye' with confidence 0.13

```

So far, following the documentation, I’ve setup the domain and story for this action as follows:

```auto
#domain_jira.yml
version: "3.1"
intents:
- jira_support
- intent_query_jira
- activate_jira_form

entities:
- jira_query_id

actions:
- action_jira
- action_validate_jira_config
- action_form_reset
- utter_jira_list
- action_query_jira

slots:
  jira_query_id:
    type: text
    influence_conversation: false
    mappings:
    - type: from_entity
      entity: jira_query_id

responses:
   utter_jira_list:
   - text: Looking up Jira...

form:
  query_jira_form:
    required_slots:
    - jira_query_id

```

I’ve setup the story as follows:

```auto
stories:
  - story: jira tasks
    steps:
      - intent: jira_support
      - action_jira #determines which jira action user wants to take. For our purposes, only query, which leads to next story
     - action_validate_jira_config

  - story: Activate jira query
    steps:
    - intent: intent_query_jira
    - action: action_form_reset #resets slots
    - action: query_jira_form #form that user enters jira ID into. 
    - active_loop: query_jira_form #Form waits for user input. Once I enter the id, I see the above error.
    - active_loop: null #close the form
    - action: utter_jira_list
    - action: action_query_jira #call to jira api

```

I’ve also set this up as a rule instead of a story, with the same result:

```auto
rules:
  - rule: activate query jira form
    steps:
      - intent: intent_query_jira
      - action: action_form_reset
      - action: query_jira_form
      - active_loop: query_jira_form
  - rule: submit query jira form
    condition:
      - active_loop: query_jira_form
    steps:
      - action: query_jira_form
      - active_loop: null
      - slot_was_set:
        - requested_slot: null
     - action: utter_jira_list
     - action: action_query_jira

```

I’ve determined that the story works up until I enter any text for the form; thats when it generates the execution failure and falls to the TED policy. I don’t know what else I can check at this point, though.

---

<div class="post-metadata">

**Author:** ![stephens](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/stephens/32/1632_2.png) [@stephens](https://forum.rasa.com/u/stephens)\
**Post date:** [February 29, 2024, 3:07pm UTC](https://forum.rasa.com/t/execution-error-for-form-action-after-migrating-from-rasa-2-8-0-to-3-6-13/61161/2 "2024-02-29T15:07:19Z")

</div>

Can you re-test, making sure you remove the story and also drop `action_form_reset`.

---

<div class="post-metadata">

**Author:** ![steve1](https://avatars.discourse-cdn.com/v4/letter/s/3da27b/32.png) [@steve1](https://forum.rasa.com/u/steve1)\
**Post date:** [March 1, 2024, 7:42pm UTC](https://forum.rasa.com/t/execution-error-for-form-action-after-migrating-from-rasa-2-8-0-to-3-6-13/61161/3 "2024-03-01T19:42:34Z")

</div>

That didn’t seem to have any change. I still receive `Execution of query_jira_form' was rejected`. I can also see in the logs that its receiving the input for the slot, the slot seems to remain empty, and it seems to think I’m calling a different, completely unrelated slot. It seems to be associated with an email intent, which is used in a separate action:

```auto
rasa.core.processor - {"parse_data_text": "JIRA_TICKET-1", "parse_data_intent": {"name": "fill_in_email", "confidence": "0.557185471057"}, "parse_data_entities: [{"entity": "email", "start": 0, "end": 11, "confidence_entity": 0.980089, "value": "JIRA_TICKET-1", "extractor": "DIETClassifier"}], "event": "processor.message.parse", "level": "debug"}

```