Nanoflow actions discontinue the nanoflow after completion
0
Hi guys, While creating a custom redirect module I've stubbed my toe on a slightly annoying issue: When running the Sign In or Open Link JavaScript actions in a nanoflow, the nanoflow is discontinued after these actions complete --> negates all logic after the JScript actions. I remember vividly that we used to be able to still continue out logic after these JScript actions in the past, they return a return variable after all. Does anyone have any idea if this is normal? If not, any pointers towards why our actions are doing this?
Yep, this is expected behaviour in Mendix client flows: Sign In and Open Link JS actions commonly terminate the running nanoflow because they cause client-side navigation (or a page reload/open) which stops the current nanoflow execution. In other words, the actions themselves can navigate away from the current app context so any logic that was still queued in the nanoflow after those actions never runs.