In the blog 'How to fix menu item navigation when using bounded taskflows' I explained how to abandon a taskflow so you could start another taskflow from the menu bar. This works fine as long as the taskflows are not started from a dynamic region.
When you use dynamic regions (so each bounded taskflow is created using page fragments) and the current application state is somewhere in a taskflow then I would expect if you use the menu bar and select the same taskflow as the application is currently in that it would restart the taskflow so it’s default start activity is executed. Without any interference this is not the case, when you use the menu and select the current taskflow nothing is happening. However if you select another taskflow there is no custom code needed to start a new taskflow.
In this blog a solution is provided to make the current taskflow restart when using the menu option.
