# Issue with Persistent Context when using q-gate

**URL:** https://discourse.nodered.org/t/issue-with-persistent-context-when-using-q-gate/50886
**Category:** General
**Created:** [10 September 2021 18:10 UTC](https://discourse.nodered.org/t/issue-with-persistent-context-when-using-q-gate/50886 "2021-09-10T18:10:07Z")
**Posts on this page:** 1
**Showing post:** 20

<div class="post-metadata">

### Author: ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)
#### Post date: [29 September 2021 19:17 UTC](https://discourse.nodered.org/t/issue-with-persistent-context-when-using-q-gate/50886/20 "2021-09-29T19:17:59Z")

</div>

I have just published `node-red-contrib-queue-gate` version 1.5.5, which should resolve the issue in Case 1. Since the node has no way of knowing whether the context store selected by the user supports synchronous operations, I have used the form for asynchronous access everywhere. Please let me know if you run into any further issues. I would be very interested in knowing whether you get any changes or improvements by running with the cache disabled.

---

_[View the full topic](https://discourse.nodered.org/t/issue-with-persistent-context-when-using-q-gate/50886)._