Rasa X Story Shows Slot Was Set Before The Intent That Sets It

[Deprecated] Rasa X Community Edition [Deprecated] Feedback on Rasa X
,
1

Hello Everyone

I’ve got a really strange bug that pops up in RASA X. It doesn’t seem to be generating the stories correctly. When providing an intent that includes a slot that needs to be set, RASA X produces the following story:

- story: Story from Conversation ID 1fc5ccd165c842bd98c14f626ca218c0
  steps:
  - intent: intent_that_requires_user_verification
  - action: utter_user_verification
  - slot_was_set:
    - EmailAddress: test@example.com
  - intent: user_verification_information
    entities:
    - EmailAddress: test@example.com
  - action: action_verify_user
  - slot_was_set:
    - verified: true
  - action: action_that_requires_user_verification

However, rasa interactive produces this story for the same input:

- story: interactive_story_1
  steps:
  - intent: intent_that_requires_user_verification
  - action: utter_user_verification
  - intent: user_verification_information
    entities:
    - EmailAddress: test@example.com
  - slot_was_set:
    - EmailAddress: test@example.com
  - action: action_verify_user
  - slot_was_set:
    - verified: true
  - action: action_that_requires_user_verification

Why does RASA X place slot_was_set before user_verification_information which actually sets the slot? It seems like RASA X is generating bad stories?

I’m using version 2.3.4 of RASA and version 0.37.1 of RASA X

RASA X was installed using the pip install for the local only version of RASA X.

Regards