# Context not updating according to flushInterval & Missing data

**URL:** <https://discourse.nodered.org/t/context-not-updating-according-to-flushinterval-missing-data/64042>\
**Category:** General\
**Created:** [17 June 2022 07:14 UTC](https://discourse.nodered.org/t/context-not-updating-according-to-flushinterval-missing-data/64042 "2022-06-17T07:14:57Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![Integration\_Chads](https://avatars.discourse-cdn.com/v4/letter/i/f14d63/32.png) [@Integration\_Chads](https://discourse.nodered.org/u/Integration_Chads)\
**Post date:** [17 June 2022 11:22 UTC](https://discourse.nodered.org/t/context-not-updating-according-to-flushinterval-missing-data/64042/6 "2022-06-17T11:22:15Z")

</div>

@zenofmud Yes you're right, though that will make the calls asynchronous as you can see [here](https://discourse.nodered.org/t/saving-context-variable-to-the-localfilesystem-immediately-on-change/28515/8).

@Paul-Reed Thank you, I tried it and it's still the same (I restarted Node-RED of course). The [documentation](https://nodered.org/docs/api/context/store/localfilesystem#options) shows it as an integer anyway since there are no quotes around it like the default of the `base` option.

---

_[View the full topic](https://discourse.nodered.org/t/context-not-updating-according-to-flushinterval-missing-data/64042)._