Hi Anjineyulu Vuddandam,
Have you recently migrated your app into a newer Studio Pro version?
Either way, have you tried updating the Marketplace modules from your application? I had one scenario where that was the problem and the solution was indeed updating the marketplace modules.
I hope you can solve your issue, best regards!
I never saw this problem, but upgrading to Mendix 9.24 might be worth a try.
I hope this helps.
Hello ;)
I don't think we have a clear answer of why this happens so the best thing to do in my opinion is to try out some different things. I would suggest to you to simply try to redeploy with a new database or simply use the built-in database from Mendix.
At least we could eliminate some of the ideas you have tried till now and narrow down towards the remaining ones.
Hi Anjineyulu Vuddandam
From the log trace I supect that Somewhere in your model, you have an activity “Call Microflow” with no valid target microflow.
This could be because:
The microflow it references was deleted.
The microflow was renamed but the reference didn’t update properly.
A Marketplace module update removed a microflow that other modules/pages still reference.
Mendix doesn’t wait until you run that page or action.During runtime initialization, it scans and loads all microflows into memory.When it finds one with a missing target, it throws this None.get
and aborts the runtime startup.
The CoreMicroflowActionFactory
is responsible for creating runtime objects for activities inside microflows.
The method createCallMicroflowAction
means: it was trying to load a “Call Microflow” activity.
None.get
means Mendix tried to look up the target microflow of that activity, but it was missing (null/empty).