StartLDAP checks entity acces (i.e., it checks if the person executing this microflow has access to the entities used)
Since the startup microflow does not check for entity access, it cannot call a microflow that does. Review your project and see if it makes sense to check for entity access and otherwise remove it.
Wait a minute, I smell a contradiction in here ;-)
1) "the startup microflow does not check for entity access" 2) "StartLDAP checks entity acces" 3) StartLDAP can be used as startup microflow
Sorry, I still don't get it. Where do I let my microflow 'check for entity access'?
Whether to use entity access on a microflow can be found under security, next to the allowed roles of the microflow.
What I meant was that your MainStartup microflow (which has a call microflow action calling the StartLDAP right?) has no entity acces defined, while the StartLDAP does, which causes the conflict.
So, check if the LDAP microflow needs the entity access defined and remove it if not, or set entity access on for the MainStartup flow.