Thanks but the problem is not verification, it’s that instead of Proxy and Implentation being deployed, I had the error message and only Implementation deployed (and added to the .openzeppelin/mainnet json). There are no more contract deployed (that i see)
Running the script again will execute upgrades.deployProxy() and I’m afraid instead of reusing the implementation, it will redo the whole thing. Right now the costs are significant so I rather deploy only the proxy and link it to the implementation manually if possible.
I assume you are deploying with Hardhat, as I didn’t see a transaction to deploy a Truffle Migrations contract.
Upgrades Plugins should pickup from where it last got to, as the implementation contract has been deployed and the address is added to .openzeppelin/mainnet.json. So it should deploy a ProxyAdmin and then the proxy contract.
Can confirm that this worked for a UUPS proxy where the implementation confirmation timed out. The timeout is hardcoded to 60 seconds (!!) which for anyone trying to pay low gas, is very low. There's a TODO in the code to make the timeout configurable, would love to see that feature