hmm the failing time is quite close to merge of PR#9050 might that be the root cause? This issue manifests if we load some models too early in the init process (when Setting was always first, then it was all cool) but now if the first loaded model is no longer Setting, it bombs if some (no idea what identifies some) is first, this happens … I’ll try to investigate why, but I guess the migration should not change just to resolve the issue, as it is not actually the root cause 
