I've had that happen 3x now since new AL went live. I was unable to fix it any of the times except by opening the SQLite database manually with a database client, turning off Write Ahead Logging, letting things process, then re-enabling WAL mode. That had an unintended side effect of making the launcher unable to write to the database at all, though it could once again read my old logins fine for a while.
After the third time, I gave up and used said db client to export every single table in the database into a big SQL file. Then I completely deleted the old database, made a new one through the launcher, and re-imported all that data via db client. THAT method worked flawlessly and I'm planning to just keep doing it that way since my autologin doesn't change very often once it's set up.
Please back up ALL the `login` database files before you try this, it's very dangerous and easy to make a mistake!