UX for password change is error prone

Hello,

First time poster, please let me know if this is not the right forum for product feedback. While this post is mainly product feedback, I'm also open to suggestions from others that may be dealing with similar issues.

In my opinion the user experience for updating passwords is very user error prone. The sequence of events appears to be:

1. A website requires a new password, presenting a form
2. 1Password recommends a new password, which is very convenient (maybe too convenient?)
3. A dialog window appears on the right asking if you want to update an existing password
4. If you submit the form before choosing an existing password, the generated password is saved into the system but not saved anywhere in 1Password!

Yes, obviously this is user error. I work in Salesforce consulting and log into environments for many clients and many sandboxes per client, all with similar domains, meaning my list of passwords to update is very long, making the small side panel scroll arduous at best. Often times I'm in a hurry, and because the recommended new password is so frictionless, I occasionally submit the form before the my brain has a chance to catch up with what I'm doing, thus I fail to select a PW to update.

I have two recommended options / ideas that make this less error prone.

1. Log a timestamped list of auto-generated passwords
   1. If I quickly realize my mistake in the scenario above, I could retrieve the PW from the list, then properly update my login
   2. Other PW management systems have this functionality
2. Have an application setting that changes the flow / process for suggested passwords, REQUIRING an item to be created or existing item selected BEFORE a password is generated
   1. I personally would immediately turn this on!

Thanks!

Steven