# Access node flag changes after the Flow mainnet network upgrade

**URL:** <https://forum.flow.com/t/access-node-flag-changes-after-the-flow-mainnet-network-upgrade/5359>\
**Category:** Node Operations\
**Tags:** access\
**Created:** [November 7, 2023, 11:04pm UTC](https://forum.flow.com/t/access-node-flag-changes-after-the-flow-mainnet-network-upgrade/5359 "2023-11-07T23:04:36Z")\
**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:** [November 7, 2023, 11:04pm UTC](https://forum.flow.com/t/access-node-flag-changes-after-the-flow-mainnet-network-upgrade/5359/1 "2023-11-07T23:04:36Z")

</div>

Hello **Access** node operators,

If you are using the `preferred-execution-node-ids` or the `fixed-execution-node-ids` configuration flag for your Access node, then please note that the execution NodeIDs will change after the mainnet network upgrade (spork) tomorrow (Nov 8th).

The new value for both of these flags **after the upgrade** should be:  
`"9686399a8a5418a12e762cfaeff2ea348c2137f554560917760e0d47acf2cda4,160241f88cbfaa0f361cf64adb0a1c9fc19dec1daf4b96550cd67b7a9fb26cd9,2b396b7fab0102f104a2af7e095b145cc14da28f863564802e158afc3e07e638,6c6af0933b710655ec553f4bead3b01c5e0a3ffd1194ee536efb926b356c54a,a080e6f3003f21d35f7ed0afc3096ab21381087a91992d7508f7be869c6edd32,92dab49c5d89fa2f0619f99131d6406a94c5f214a198aafab41241322f9bf173"`

If you are not using the flags, you do not have to make any changes.

_These flags are optional and only apply to the access nodes._

Thank you,  
Flow Foundation
