Does clearing of autocommited objects trigger delete behaviour?

When you create an new object that has an association to child objects all child objects are deleted when you rollback/cancel your new parent object. However very often users do not actually press the cancel button but instead the navigate away or close their browser screen. To prevent this Mendix implemented this system where they delete objects to prevent database corruption. But it appears that this does not trigger delete behaviour. Is this correct? Some autocommitted objects still existed on logout for session 'Anonymous_a35680ec-e2f3-47f9-91ec-ec2637551c94'. Autocommitted objects are newly created objects which were not yet committed, but are inserted into the database because an associated object was committed. Autocommitted objects should explicitly have been committed, please check your model and apply the necessary changes. The autocommitted objects have been deleted from the database to prevent database corruption.Number of autocommitted objects per type which still existed for this session: - MyFirstModule.Company: 1 object(s).
1 answers

That is correct, there is already a ticket for this with number 18082. The change in itself is trivial, we just haven't thought about the impact enough to change this now.

That said, I can't see any immediate problems and that ticket isn't currently very high in the priority queue, If you want this fixed, you could file a ticket yourself to get some attention to this issue again.