This proposal cannot be executed right now because there are older pending transactions in the Gnosis Safe

Support Defender
1

Hello,

we need to help with stucked proposal, we dont know what to do to execute the transaction.

:computer: Environment
Admin, Fantom network with forked gnosis here: safe.fantom.network

:memo:Details

we have this Defender proposal:

https://defender.openzeppelin.com/#/admin/contracts/fantom-0xA3b52d5A6d2f8932a5cD921e09DA840092349D71/proposals/ef9187bd-b1cc-4fbb-870f-58a8f80f98c0

and we cannot execute it, because of this error:

"Transaction would revert. Check that permissions, balances, and other function requirements are valid for the transaction you want to run."

We think that its correct, transaction would fail and we have second proposal which we want to execute before (and other ones) which will fix the reason, why original proposal would fail.

https://defender.openzeppelin.com/#/admin/contracts/fantom-0xA3b52d5A6d2f8932a5cD921e09DA840092349D71/proposals/d0edf4d5-50c1-41bf-837b-bec5c57801ca

It says: "This proposal cannot be executed right now because there are older pending transactions in the Gnosis Safe."

:1234: Code to reproduce
In previous details

What can we do to enable new proposal to came through defender? I can archive the first one which is failing, but will second proposal working immediately or it will not help and we loose handle to this failing one?

Or should we execute some other transaction in gnosis, which will cause this first failing one will be deprecated, cannot be executed, because other transaction in gnosis happen, but will it help the second proposal to come trough?

2

Hi @arcadecrypto, in this case you should not archive the first proposal, but reject it. That will execute a "no-op" TX with the same nonce as the actual proposal TX.

Once you confirm the rejection of the first proposal, your second proposal should become the next in line and get unblocked.

3

it cannot be rejected. We tried to reject multiple times, multiple proposals. First one can reject it (we still need quorum), but second one can click on reject. It will open MetaMask for signature. Confirm it but there’s still 1/n visible as confirmed