Show Page in Nanoflow Not Navigating During Quote Creation Flow (Works on Refresh)

0
Hi all, I'm facing a page navigation issue in my Mendix app and could use some help.   I'm using a nanoflow to create a persistable Quotation object, and then trying to navigate to a page using Show Page. This works perfectly when triggered from the homepage or after a page refresh, but when the same nanoflow is triggered from the Quote creation flow, the Show Page activity does not load the UI screen. The navigation seems to silently fail — no error messages in the Mendix console or UI, and the flow doesn't proceed visually, although backend logic executes.   I’ve tried multiple things: Ensuring the object is persistable and created correctly Passing the object to a microflow (for additional setup) before Show Page Trying both committed and uncommitted states of the object Simplifying the target page (removing reference selectors, list views, etc.) Adding a JavaScript delay before calling Show Page Monitoring browser dev tools (I see a Chrome warning:"Throttling navigation to prevent the browser from hanging. See https://crbug.com/1038223") Interestingly, the Show Page works if I refresh the browser, and try again from the same context. There are no issues with other logic which is added in the nanoflow.   Has anyone encountered this kind of behavior before?   Any ideas on how to ensure Show Page reliably navigates from within the Quote creation flow?   Thanks in advance! Poojitha  
asked
2 answers
0

Hi poojitha,

                

  1. Use a microflow to:

    • Create + commit the object

    • Return the object

  2. Then use a nanoflow to:

    • Take the returned object

    • Show Page

This pattern ensures server-side commit + client-side navigation.

answered
0

Do you have security set to Demo/Production, or Production? If yes, then it pays to check the Security tab in the module to see if pages, MFs, NFs, Entity Access permissions are right, and if in the App Security tab, your user role is set for the module you're programming.

If that's not set then debugging step by step and looking for errors in the console log is a way. Maybe there are even smarter answers from the community than mine in that case :-).

answered