# Config node context and persistency after deployment

**URL:** <https://discourse.nodered.org/t/config-node-context-and-persistency-after-deployment/89354>\
**Category:** Developing Nodes\
**Created:** [8 July 2024 14:17 UTC](https://discourse.nodered.org/t/config-node-context-and-persistency-after-deployment/89354 "2024-07-08T14:17:49Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Thomassorensen](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/thomassorensen/32/45692_2.png) [@Thomassorensen](https://discourse.nodered.org/u/Thomassorensen)\
**Post date:** [13 July 2024 19:45 UTC](https://discourse.nodered.org/t/config-node-context-and-persistency-after-deployment/89354/6 "2024-07-13T19:45:02Z")

</div>

Thats not a bad idea, that is probably the way I need to go, but it still seems like a bug that it's not consistent with how normal node context works.

> [@Node Context does not reset on redeploy](https://discourse.nodered.org/t/node-context-does-not-reset-on-redeploy/14733/3):
>
> 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/config-node-context-and-persistency-after-deployment/89354)._