This should be fixed in version 7.23
“We fixed an issue where an object which was initially auto-committed and then explicitly committed in a before-commit action was still treated as auto-committed one. (Ticket 78384)”
And i believe it’s a broader fix than just before-commit actions. Because I used to have a similar issue as you’re describing in versions 7.16 – 7.21 or something like that. And it’s fixed since i upgraded.
Hi Cecile,
Short answer: autocommitted isn't actually committed.
You always need to explicitly commit your objects in your microflow, otherwise objects will be removed on logout. This includes autocommitted objects.
Objects can become autocommitted, if they have a reference to an object which is committed to the database.
The example Mendix always uses is Creating an OrderLine within an Order, and committing the Orderline, will autocommit the Order, since the association parent is OrderLine: