# \[CANCELLED\] Flow mainnet height coordinated upgrade on Thursday Feb 13th, 16:00 UTC

**URL:** <https://forum.flow.com/t/cancelled-flow-mainnet-height-coordinated-upgrade-on-thursday-feb-13th-16-00-utc/7076>\
**Category:** Node Operations\
**Created:** [February 11, 2025, 11:54pm UTC](https://forum.flow.com/t/cancelled-flow-mainnet-height-coordinated-upgrade-on-thursday-feb-13th-16-00-utc/7076 "2025-02-11T23:54:29Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vishal](https://avatars.discourse-cdn.com/v4/letter/v/49beb7/32.png) [@vishal](https://forum.flow.com/u/vishal)\
**Post date:** [February 11, 2025, 11:54pm UTC](https://forum.flow.com/t/cancelled-flow-mainnet-height-coordinated-upgrade-on-thursday-feb-13th-16-00-utc/7076/1 "2025-02-11T23:54:29Z")

</div>

The height cooridnated upgrade on mainnet for Feb 13th been postponed to next week.

No changes need on the node as of now.

Please ignore 👇

Hello Flow Node Operators,

There will be a height coordinated upgrade on Flow mainnet on Monday, Feb 13th at 16:00 UTC.

Please be prepared to update your Flow nodes on that day.

**Actions needed from your side on Feb 13th:**

* * *

1. **Verification** , **Collection** and **Consensus** node operators -

Please update your docker to the new tag that will be provided that day as part of an announcement and restart the node.

Do **not** delete the data folder.

_Please complete this action within 24 hour of the announcement_

_If you are running multiple nodes, please restart the nodes one after the other (instead of all at once)._

* * *

1. **Access** node operators -

Please update your docker to the new tag that will be provided that day as part of an announcement and restart the node.

Do **not** delete the data folder.

* * *

1. **EVM Gateway** operators -

Please update the EVM Gateway to [v1.0.3](https://github.com/onflow/flow-evm-gateway/releases/tag/v1.0.3) at 16:00 UTC.

* * *

1. **Execution** node operators -

Execution nodes will stop executing blocks at a particular height and must be restarted with a new docker tag.  
You can monitor the block height by querying the metric execution\_runtime\_last\_executed\_block\_height.  
e.g. `curl -s [http://127.0.0.1:8080/metrics](https://www.google.com/url?q=http://127.0.0.1:8080/metrics&sa=D&source=calendar&ust=1739747589032206&usg=AOvVaw0lDfRfD_RgmeUD4US-3uFt) | grep -E '^(execution_runtime_last_executed_block_height)'`

Once the execution node has stopped executing blocks, the height reported by the metric will no longer advance.  
One that happens, do the following:

1. Stop the node
2. Remove the following config params if you have them set. These are no longer needed and need to be removed.

```auto
--evm-tracing-enabled
--evm-traces-gcp-bucket=xxx

```

1. Update the docker tag to the one provided that day.
2. Start the node.

Do **not** delete the data folder.  
_Please complete this action immediately for the execution node_

* * *

This is **NOT** a spork, and the network will keep running during the upgrade.~~

Thank you for your cooperation,  
Flow Team.

---

<div class="post-metadata">

**Author:** ![vishal](https://avatars.discourse-cdn.com/v4/letter/v/49beb7/32.png) [@vishal](https://forum.flow.com/u/vishal)\
**Post date:** [February 12, 2025, 6:47pm UTC](https://forum.flow.com/t/cancelled-flow-mainnet-height-coordinated-upgrade-on-thursday-feb-13th-16-00-utc/7076/2 "2025-02-12T18:47:22Z")

</div>

Please note - the mainnet update for tomorrow has been postponed to next week. We will share the date and time soon.  
Sorry for the inconvenience.