I've been using Vault for about a year and slowly converting all my business and personal passwords to unique strings as long as each site will allow me to use. Just about every time I try this, there's some sort of problem that extends the time it takes to get to a "save password" prompt beyond 120 seconds, meaning that the generated password is permanently lost and I have no way of logging in to the portal in question after changing the password. Every single time.

The solution I've been forced to use is to open Notepad, generate a password, paste it into an empty text file (bypassing all the security features offered by Vault), then go through the task of inputting the new password into the portal, answering often multiple security and MFA prompts, being allowed into the portal which goes unnoticed by Vault because it doesn't offer to save the new password, logging out of the portal, logging back in with the new password (copied from Notepad because Vault has long ago cleared the clipboard), answering MFA again and only then being offered the option to save the password. 

Vault needs to detect that I'm setting or changing a password sooner and either temporarily extend the clipboard clearing feature's timeout or save the password in some staging area where it remembers both passwords until it's told which one is correct. Or if the password is new, it must hold on to the password through the entire registration process on the off chance that it never reaches a state where it sees the "registration complete" state where it offers to save the password, because it's not always possible to reset credentials on accounts you've just created minutes ago. 

I've recently figured out that Windows Clipboard Manager (WinKey+V) keeps the password in the clipboard history even if Vault tries to clear it so I'm able to use that instead of Notepad but I shouldn't have to try to outsmart the software because it keeps forcibly forgetting the passwords it's supposed to safeguard.

Please also either enable merging similar credentials or add a feature that goes through all my passwords when it detects a password update, filters by the TLD and asks if I want to update all the entries that used the old credential to the new password. I very often come across instances of a different username and password being stored for a website, simply because it uses variations of the login URL like "login.domain.com," "login.secure.domain.com," "auth.domain.com," etc. Vault should be able to detect multiple entries of the same credential and either deal with it automatically, or ask me if I want to merge credentials by just adding a URL to the existing entry instead of creating a new one.