# Execution Node ACTION REQUIRED

**URL:** <https://forum.flow.com/t/execution-node-action-required/2841>\
**Category:** Node Operations\
**Created:** [February 17, 2022, 12:07am UTC](https://forum.flow.com/t/execution-node-action-required/2841 "2022-02-17T00:07:22Z")\
**Posts on this page:** 1\
**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 17, 2022, 12:07am UTC](https://forum.flow.com/t/execution-node-action-required/2841/1 "2022-02-17T00:07:22Z")

</div>

Hello Flow Execution Node Operators,

We discovered an issue with the Execution node software. There was a new field - `ExecutionDataID`, that was added in the Execution result which an Execution nodes produces. The value of the field was not being calculated consistently by all the execution nodes when they executed a transactions that threw an error. This resulted in blocks not being sealed. We have resolved this by setting the `ExecutionDataID` to be a fixed value for now. This is the [commit](https://github.com/onflow/flow-go/blob/v0.24.5/engine/execution/computation/manager.go#L314-#L319) in the code.

If you are running an Execution node, please do the following:

1. Stop the node

2. Run the rollback script.

The script can be downloaded from [here](https://storage.googleapis.com/flow-genesis-bootstrap/util.tar)

i. `wget https://storage.googleapis.com/flow-genesis-bootstrap/util.tar`  
ii. `tar -xvf util.tar`

Alternatively, you can build it from the [source](https://github.com/onflow/flow-go/tree/1209f20fb01fa0556dd19877caec3ceb7f84f615/cmd/util)

Then run,  
**`./util rollback-executed-height --datadir /var/flow/data/protocol --height 24188132`**

The script removes all the execution results starting from block height 24188132 up till the latest executed block by the execution node. This is done because the execution results have the `ExecutionDataID` field calculated inconsistently and removing the results will allow the node to re-calculate these results using the new code which guarantees the results to be consistent.

Make sure the script completes successfully before proceeding to the next step.

1. Upgrade the node to docker image: **v0.24.5** (alternatively v0.24.5-without\_netgo)

2. Start the node.

_No action is needed for any other node type._

Thank you,  
Vishal