Data Source Microflow Blocking Page Load in One App but Not in Fresh App (Lazy Loading Behavior Difference)
0
Hi everyone, I have a strange issue related to data source microflow loading behavior. Here’s my scenario: I have a page that contains a Data View. The Data View’s data source is a microflow. I placed a breakpoint inside that microflow. When I open this page in my existing application, the breakpoint is triggered immediately, and the page does not open until I continue the microflow. A progress bar keeps showing until the microflow finishes. This clearly means the data source microflow is not lazy loaded — it must finish execution before the page loads. However, when I created a fresh new Mendix app (same Mendix version) and implemented the exact same setup, the behavior was different: The page loads first, and only then the data source microflow runs (with the breakpoint still active). So here, the data source is clearly lazy loaded. I’ve verified that: Both apps are on the same Mendix version. The page and microflow configurations are identical. This makes me think: Lazy loading seems to be the default Mendix behavior, as Maya AI also confirms that pages load first and then the data source microflows run. But in my existing application, something is forcing the data source to run before the page opens. Also, note that multiple UI developers have worked on this existing app before, so I suspect that some custom JS or code modification might be affecting this. My questions: Why is my existing application not showing lazy loading behavior while a fresh one does, even with identical configurations? What kind of custom code or configurations (e.g., widget overrides, custom JS, page-level settings, or themes) could make the data source microflow block the page load? How can I identify and revert such a behavior to restore lazy loading? Any insights or similar experiences would be really helpful! Thanks in advance.
asked
Rishi Sundar
1 answers
0
Default behavior is lazyloading.
Things to try:
- create a new page in your current app, adding the same dataview and datasource. See if this page opens before the microflow is finished.
- search in your project-directory in /javascript for any *.js file that contains code that makes the page wait. Delete it, see if any error-message shows up in Studio
- check your page for any js-triggers, like html-widget for instance
- check the layout that your page uses (if not Atlas_default)
Don't know if Maia is correct, but it answered this to my question:
And there is a widget to make the page open and only trigger a datasource microflow once it is in a visible view:
answered
Tim van Steenbergen