You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After transactions are successfully executed, the UI's listing is not updated. The transaction is still displayed as an item that's pending execution, and when you try to execute it again it will fail (as expected). But only then does the UI update.
Environment
Browser: Chrome
Wallet: MetaMask
Safe: 0xCe3Bd9Bb075Bdb1bc999349fc045ba021B774C13 (but should be easily reproducible on any)
Environment: production (Celo mainnet)
Steps to reproduce
Set up a multisig with 2 owners
Create "send funds" transaction
Sign from both owner's wallets and execute transaction
Confirm on block explorer for GnosisProxy that transaction was confirmed
Confirm that UI still has transaction (shown as pending execution)
Attempt to execute transaction again (might have to manually set gas limit because execution preview fails)
Confirm that UI now clears the transaction
Confirm on block explorer that failed transaction shows up
Expected result
Transactions that are executed are cleared automatically in UI
Obtained result
Transactions that are executed stay in UI's transaction listing and are not cleared until you try to execute the transaction again (at which it will fail again!)
Description
After transactions are successfully executed, the UI's listing is not updated. The transaction is still displayed as an item that's pending execution, and when you try to execute it again it will fail (as expected). But only then does the UI update.
Environment
Steps to reproduce
Expected result
Transactions that are executed are cleared automatically in UI
Obtained result
Transactions that are executed stay in UI's transaction listing and are not cleared until you try to execute the transaction again (at which it will fail again!)
Screenshots
https://www.loom.com/share/8d8287dd9ec04937a11691f647a33802
The text was updated successfully, but these errors were encountered: