I’m encountering an issue with the two-stage fallback policy. Slots are getting reset during the native action “action_revert_fallback_events” causing entities to be lost during the dialogue. We found some workarounds on the forums, however, they require a code change in the rasa core sdk library. [https://github.com/RasaHQ/rasa/issues/3281](https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_RasaHQ_rasa_issues_3281&d=DwMFaQ&c=H50I6Bh8SW87d_bXfZP_8g&r=6VEExljb7Qf1nP9By5mnhVeaHaSM9SVkY8XX11JU3PQ&m=eIuN_HvKQQlXNOpDcUN9KedEyS_Ka-A2zYsyyBGnYUs&s=GyoW4VewZ0gUQoeWrfrBU-v-9fA0d64iQhVpuY13KEI&e=) [http://forum.rasa.com/t/help-twostagefallbackpolicy-do-not-revert-slot-filling-after-affirmation/5607](https://urldefense.proofpoint.com/v2/url?u=https-3A__forum.rasa.com_t_help-2Dtwostagefallbackpolicy-2Ddo-2Dnot-2Drevert-2Dslot-2Dfilling-2Dafter-2Daffirmation_5607&d=DwMFaQ&c=H50I6Bh8SW87d_bXfZP_8g&r=6VEExljb7Qf1nP9By5mnhVeaHaSM9SVkY8XX11JU3PQ&m=eIuN_HvKQQlXNOpDcUN9KedEyS_Ka-A2zYsyyBGnYUs&s=JtYDtFwfncBL6E2cGF4WS6NqnVVRoNSxKcgpB-rkFOQ&e=) Is there a workaround that would not require modification of the rasa core code? Ex. Chat History # Bot You ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── 1 action_listen ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── 2 approve intent: restart_vacation_request 0.20 ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── 3 action_default_ask_affirmation 1.00 Sorry I do not understand that, could you rephrase? action_listen 1.00 ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── 4 /approve_vacation_request{"requester": "John Doe", "range": "06/12/2019 - 06/12/2019", "person": "Jane Doe", "comment":""} intent: approve_vacat…

Will be fixed in rasa 1.1.8 :slight_smile:

Yes, the action_revert_fallback_events does exactly what it says it does – it undoes anything that was done before, because it assumes that it falls back because something went wrong, i.e. any slots set probably shouldn’t have been set. I understand what you mean though – if the user rephrased, and that was taken with high confidence, the events of the previous (unclear) action should be reverted, but not the rephrased intent. So ideally it would look something like action_revert_fallback_events 1.00 rewind slot{"comment": ""} slot{"person": ["John Doe"]} slot{"range": "06/12/2019 - 06/12/2019"} slot{"requester": "Jane Doe"} action_listen Do you agree?

Yes, that is the ideal flow. Is there any workaround for this?

Hm, it might be that we need to change the behavior. @Tobias_Wochinger can you check this out and tell me what you think?

[image] fishnyips: Slots are getting reset during the native action “action_revert_fallback_events” causing entities to be lost during the dialogue. Actually these should be set again when the intent is applied to the tracker. Which Rasa (core) version are you using? Hm, it might be that we need to change the behavior. @Tobias_Wochinger can you check this out and tell me what you think? Not entirely sure, whether I understand you two correctly. action_revert_fallback_events reverts all events from the TwoStageFallbackPolicy and re-applies the rephrased user message. Slots from entities are also reset (or should be)

Right, but as you can see above, it seems to apply the rephrased user message before reverting, which gets it reverted: slot{"comment": ""} slot{"person": ["John Doe"]} slot{"range": "06/12/2019 - 06/12/2019"} slot{"requester": "Jane Doe"} action_revert_fallback_events 1.00 rewind rewind action_listen Slots from entities are also reset (or should be) Should the ones from the re-applied, rephrased (accepted with high confidence) input be reverted?

It is not reset. See here for people experiencing the same issue: [image] [HELP] TwoStageFallbackPolicy: do not revert slot filling after affirmation Rasa Open Source Hi, rasa-core==0.13.1 I am using the TwoStageFallbackPolicy. Within the action ‘action_default_ask_affirmation’, I have a button for affirmation with the payload containing an intent and entities from a user message that has to be affirmed, e.g., {'title': 'Yes', 'payload': '/inform{"location":"berlin"}'} Let’s say I have a slot ‘location’ that is filled with the value of the corresponding entity. However, when a user affirms, ‘action_revert_fallback_events’ reverts not only fallback events …

@fishnyips This bug was fixed in newer rasa versions. Can you to use the latest version rasa 1.x ?

@Tobias_Wochinger I am using Rasa version 1.1.7 and I am still experiencing this issue.

This was actually an issue! Thanks for pointing this out! Fixing it in Fix twostage il by wochinge · Pull Request #4100 · RasaHQ/rasa · GitHub

When should we expect the release for 1.1.8?

Two-stage fallback policy slot reset

Rasa Open Source

fishnyips (Crys) July 19, 2019, 2:36pm 7

It is not reset.

See here for people experiencing the same issue:

Topic		Replies	Views
[HELP] TwoStageFallbackPolicy: do not revert slot filling after affirmation Rasa Open Source	7	1293	May 8, 2019
Two-stage fallback resets all slots in Rasa 2.0.0 Rasa Open Source	0	511	October 23, 2020
Slot value resets to None Rasa Open Source	8	1507	July 28, 2021
[HELP] two stage fallback policy removes slot which was set in a custom action Rasa Open Source	4	1100	March 6, 2020
Setting a Slot in default fallback whilst using "UserUtteranceReverted()" Rasa Open Source	5	873	September 11, 2021

Two-stage fallback policy slot reset

Related topics