You may opt to call a nanoflow to start your actions.
Within nanoflow all actions are executed in separated transaction.
That way you can have a nanoflow calling multiples Microflows…
Another option is having SUB_Microflows with Errorhandling set to Custom Without-rollback.
There is other options like Community Commons or Custom Java Actions
OJO: Check this thread for more info on Mendix Commit behavior : https://forum.mendix.com/link/questions/117637
You can use the 'EndTransaction' activity from the CommunityCommons module.
EndTransaction– This commits the transaction, which will end the transaction or remove a save point from the queue if the transaction is nested.