Yes, it will, but this is kind of tricky.

When a user logs out objects in cache coupled to his/her session will also be removed. This means as long as you only use local variables in your microflow or objects from the database it's no problem, but as soon as you use earlier changed objects which are not yet committed in the database (e.g. an object changed in a dataview with a button triggering the mentioned microflow) this could lead to unexpected results. As the object does not exist in cache anymore, it will be retrieved from the database, which means the changes on the object are lost.

A user should be probably be aware it's not such a good idea to exit the browser when starting a long running microflow (e.g. an import), but on the other hand we should not depend on users' behaviour. Therefore, when you model such a microflow you could prevent unexpected results by not having to use changes from objects which are only present in cache in your microflow (e.g. by committing the object first before starting the microflow).

Yes. Because the user is logged in when triggering the microflow, it will be executed completely (if no errors occurred). It makes no difference if you log out in the meanwhile.

Yes! When a user triggers a Microflow it will be completely executed; regardless of the status of the user (whether he logs out or remains logged in).

Yes! When a user triggers a Microflow it will be completely executed; regardless of the status of the user (whether he logs out or remains logged in).