Assuming that you are running the MF from a button, open the properties and go to the mircoflow settings to change the microlfow call type from synchronous to Asynchronous. Then the timeout will no longer apply and there is no need for more complex settings. Some insights are found here: https://www.mendix.com/blog/take-a-time-out-to-learn-about-asynchronous-calling/
In response to your comment, it is possible to run sub microflows asynchronous with the help of the community commons module (https://docs.mendix.com/appstore/modules/community-commons-function-library):
RunMicroflowAsyncInQueue – This runs a microflow asynchronously (meaning, this function immediately returns and schedules the microflow to be run in the near future). The queue guarantees a first-come-first-serve order of the microflows, and only one action is served at a time. The microflow is run with system rights in its own transaction. This is very useful for running heavy microflows in the background.
executeMicroflowInBackground – This is similar to
RunMicroflowAsyncInQueue, but it accepts one argument as parameter.
If this works for your situation I don’t know if subsequent actions depend on previous actions you need to resdign the flow for example as the actions are sort of fire and forget.