# Error at the end of scheduling a timelock upgrade

**URL:** <https://forum.openzeppelin.com/t/error-at-the-end-of-scheduling-a-timelock-upgrade/22967>\
**Category:** Upgrades\
**Tags:** proxies, upgrades, hardhat\
**Created:** [January 19, 2022, 2:38pm UTC](https://forum.openzeppelin.com/t/error-at-the-end-of-scheduling-a-timelock-upgrade/22967 "2022-01-19T14:38:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Felix\_Theodoor](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/felix_theodoor/32/2628_2.png) [@Felix\_Theodoor](https://forum.openzeppelin.com/u/Felix_Theodoor)\
**Post date:** [January 19, 2022, 2:38pm UTC](https://forum.openzeppelin.com/t/error-at-the-end-of-scheduling-a-timelock-upgrade/22967/1 "2022-01-19T14:38:32Z")

</div>

Hi OpenZepp community,

I am currently at step 27. in the following guide:

# [Tutorial on Using a Gnosis Safe MultiSig with a TimeLock to Upgrade Contracts and use Functions in a Proxy Contract](https://forum.openzeppelin.com/t/tutorial-on-using-a-gnosis-safe-multisig-with-a-timelock-to-upgrade-contracts-and-use-functions-in-a-proxy-contract/7272)

receiving following error when executing the schedule timelock:

```auto
Confirmation transaction failed - Transaction has been reverted by the EVM: { "blockHash": "0xdb6198fc5c49065a1227b5852df29fc05fd0fbe21b2be6305fbfc38173e02adc", "blockNumber": 10018669, "contractAddress": null, "cumulativeGasUsed": 74374, "effectiveGasPrice": "0xb2d05e00", "from": "0xbe35035bbc968cfc28cf7f6359d3223f78375445", "gasUsed": 74374, "logsBloom": "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000", "status": false, "to": "0xc7a4e77e7d97d70517f28c0edfea9c5ac314d7e1", "transactionHash": "0xccb2c91fe5efc9e91c3179fe86a53193e0bb14e021c05628a935b22d50c6c31b", "transactionIndex": 0, "type": "0x2", "events": {} }

```

MetaMask would automatically have gas limit set to 0 when trying to execute the transactio, also; manually setting the gas limit to a number which wont get rejected provides abovestated error.

Anyone having a thought?

---

<div class="post-metadata">

**Author:** ![frangio](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.openzeppelin.com/frangio/32/15251_2.png) [@frangio](https://forum.openzeppelin.com/u/frangio)\
**Post date:** [January 26, 2022, 10:30pm UTC](https://forum.openzeppelin.com/t/error-at-the-end-of-scheduling-a-timelock-upgrade/22967/2 "2022-01-26T22:30:11Z")

</div>

Sorry there are many reasons why this could be failing... It's difficult to guess.