# Node Context does not reset on redeploy

**URL:** <https://discourse.nodered.org/t/node-context-does-not-reset-on-redeploy/14733>\
**Category:** General\
**Created:** [24 August 2019 07:36 UTC](https://discourse.nodered.org/t/node-context-does-not-reset-on-redeploy/14733 "2019-08-24T07:36:02Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [24 August 2019 08:16 UTC](https://discourse.nodered.org/t/node-context-does-not-reset-on-redeploy/14733/3 "2019-08-24T08:16:54Z")

</div>

> [@g4ocq](#):
>
> I assume as I am not specifying InFile it should be stored in memory and get re-initialsed after a change to the node, if thats not the case I am looking for a way to re-iniatalise these values when I make small changes

No. Deploying a change does not reset context.

You could create a flow that sets your context values to undefined (which is how you delete them) and start it with an Inject node configured to fire on start.

---

_[View the full topic](https://discourse.nodered.org/t/node-context-does-not-reset-on-redeploy/14733)._