Consider an Ergo instance where always-on is opt-out or mandatory. If you create an account with SAREGISTER, no client object will be created immediately. But the next time you restart Ergo, a client object will be created by createAlwaysOnClients, and it will assume that the stored modes (am.loadModes(accountName)) represent the actual desired modes instead of applying the configured default user modes. But these modes will be empty, so in the typical deployment, these clients will not have +i as expected.