# \[NEW FEATURE\] node-red-contrib-queue-gate (version 1.2.0)

**URL:** https://discourse.nodered.org/t/new-feature-node-red-contrib-queue-gate-version-1-2-0/14506
**Category:** Share Your Nodes
**Created:** [19 August 2019 22:14 UTC](https://discourse.nodered.org/t/new-feature-node-red-contrib-queue-gate-version-1-2-0/14506 "2019-08-19T22:14:44Z")
**Posts on this page:** 1
**Page:** 1

<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: [19 August 2019 22:14 UTC](https://discourse.nodered.org/t/new-feature-node-red-contrib-queue-gate-version-1-2-0/14506/1 "2019-08-19T22:14:44Z")

</div>

This update adds the option of persistence for the state of the gate and the contents of the queue. (See Github, [issue #6](https://github.com/drmibell/node-red-contrib-queue-gate/issues/6) )

Previously, the node would enter the Default State on startup, either when first deployed in the editor, re-deployed as part of a modified flow or entire workspace, or when Node-RED is restarted by the user or by a system service. Now, however, the user can select the `Restore from saved state` option (checkbox) in the edit dialog. Then, if a persistent form of context storage has been enabled in the Node-RED settings.js file, the node will attempt to enter the state last saved in the node context and restore the contents of the message queue. It will use the Default State (with an empty queue) only if no saved state is available.

This update also corrects a bug, similar to the one in `node-red-contrib-simple-gate`, that would cause an [error](https://discourse.nodered.org/t/i-am-not-understanding-this-error-message-i-get-when-nr-starts/14075/15) when the `msg.topic` is not a string.

Please report bugs or issues here or on [GitHub](https://github.com/drmibell/node-red-contrib-queue-gate/issues).