You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 15, 2025. It is now read-only.
Hi,
Have found this issue using the latest version of the LeaveAction widget, on Mx 8.6.4, and can replicate it consistently. This is happens when using either Exclude, or Include.
If the user is on a page, and calls a microflow which uses a Validation Feedback action to show an error to an input field on that page, and then the user leaves that page using a method that should trigger the LeaveAction (for example closing their browser window) - the leave action no longer fires.
If this Validation Feedback is not called/displayed, then the LeaveAction still fires at the expected triggers.
Hi,
Have found this issue using the latest version of the LeaveAction widget, on Mx 8.6.4, and can replicate it consistently. This is happens when using either Exclude, or Include.
If the user is on a page, and calls a microflow which uses a Validation Feedback action to show an error to an input field on that page, and then the user leaves that page using a method that should trigger the LeaveAction (for example closing their browser window) - the leave action no longer fires.
If this Validation Feedback is not called/displayed, then the LeaveAction still fires at the expected triggers.