Backup ID not being sent to database

We have a couple users where they changed their passwords and then forgot them a couple days later

When we go to the recovery database the current id is not backed up to the database

Has anyone else seen this?

Subject: Check the local log file on the client

Starting in 8.0, a great deal of ID file recovery-related information will be placed into the client’s local log file, including if a backup is needed and why, when backups were attempted, and if they succeeded or not.

Subject: Recovery not updated

when a user changes their password their copy of their id goes to a database where would then be able to recover the id to extract a password

Subject: That could be the source of the confusion

New encrypted backup copies are not sent to the repository every time the user changes his or her password – that would flood the database with identical content encrypted in different ways. The encrypted backups are not protected with a password, they are protected with a randomly generated encryption key that can only be unlocked through the ID File Recovery process.

New encrypted backups are only sent out when something significant changes in the content of the ID file, such as a new key pair, a new name, a new internet key or cert, a new document encryption key, and so on.