Given the following module hierarchy:
<pre>
...
   \_ mid_level_module
                      \_ auto_install_module
                      \_ module_with_data_error
</pre>
Where:
* The auto install module has (for sake of example) some a model override of `ResCurrency` that defines a new method for the class. This module also has some data that defines an `IrCron` record, which executes the method added by the `ResCurrency` override within its own model files.

* The data error module has a view extension which has some bad syntax that will trigger a failure in `load_data()`.

Upon running an odoo instance with `-i module_with_data_error`, the module load will proceed until failing at this module- however the CRON data loaded from `auto_install_module` will be in the `ir_cron` postgres table, while its overridden method is not in the registry.

***

The problem occurs because a package's data/schema changes are committed prior to actually marking the module record as installed- so the mark install step doesn't get committed until the subsequent package data/schema changes are committed.

When the data_error module fails to have its data loaded, we will reset `to_install` modules as `uninstalled`- but because the module state changes from the prior package (auto_install) were not yet committed, it will not attempt to reinstall this package upon re-initialization (receiving a new request which un-rests the server).

So we are left with the CRON record which was committed already, without the actual model override required for the CRON to run.

***

If we modify the module state before committing, the issue is no longer present.