The issue is related to the latest MetaMask extension version 12.11.0.

You may encounter this problem when executing multiple transactions sequentially—specifically when a second transaction is triggered immediately after the successful completion of the first transaction.

In this version, the first MetaMask pop-up functions correctly, but the second pop-up may indicate a failure, even though the transaction will eventually be confirmed on the blockchain.

My observation is that if you do not close the extension—something you might do after the first transaction by clicking the "Close Extension" button—the next transaction loads within the same pop-up. This causes it to use outdated values from the initial load, leading to a simulated failure. However, the transaction does not fail in reality, as the previous transaction on the blockchain has already been completed.

FYI, this issue does not occur if you close the extension after the first transaction and allow a new pop-up to open for the next transaction.