Following the migration sql table initialization in RUNTIME-3703, if a population was unavailable at the execution of the migration, their version are not updated and the initialization will be re-executed, resulting in a failed migration.

This case can be reproduced by having a missing conf parameter at startup before the first execution of the script. This will start the app in safe mode, disabling other population hence not migrating them