See the documentation here: https://docs.mendix.com/refguide/object-activities
Having autocommitted objects are always modeling errors. You forgot to do a commit on newly created objects somewhere.
Regards,
Ronald
The check ‘commit’ in activities Create and Change intuitively is the developer saying to the database management of Mendix,
Instead “if not checked” Mendix might not commit the change at all. This is a very big error by the Mendix Business Server. No Database-engine should ever drop data. A good thing to know is that Chris de Gelder's idea of removing this feature is planned for implementation. Please upvote this idea, as it might speed up things a bit.
For now, find out which Create or Change activity you have not marked the commit-check and mark it so it gets committed right away.