Core warning concerning autocommitted objects

I came across next warning in the console of the modeler when my app was running:   I would like to know why the autocommitted objects are deleted instead of actually getting committed. I know I could probably solve this by explicitly committing my objects, but lets just say I don't want to that in this case. Could anyone give me some more explanation?   Kind regards
1 answers

Mendix considers autocommitted objects a modelling error, from the documentation:

" If you end up with autocommited objects, it is always because of a modeling error. At some point in time, an association was set to a new object, the associated object was committed, and all of its associations were committed as well to keep all the data consistent."

From this point of view, it makes sense to not commit them, since they would persist the result of a modelling error.