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

**URL:** <https://discourse.nodered.org/t/new-feature-node-red-contrib-queue-gate-version-1-3-0/15481>\
**Category:** Share Your Nodes\
**Created:** [12 September 2019 19:36 UTC](https://discourse.nodered.org/t/new-feature-node-red-contrib-queue-gate-version-1-3-0/15481 "2019-09-12T19:36:30Z")\
**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:** [12 September 2019 19:36 UTC](https://discourse.nodered.org/t/new-feature-node-red-contrib-queue-gate-version-1-3-0/15481/1 "2019-09-12T19:36:31Z")

</div>

[Node-red-contrib-queue-gate](https://flows.nodered.org/node/node-red-contrib-queue-gate) is a node for controlling message flow, including message queueing capability. This update adds the option to change the behavior of the `toggle` command. Previously, this command could only switch the node between the `open` and `closed` states, with no effect on the `queueing` state. In the new version, the effect of the `toggle` command depends on the option selected using the `Toggle between open and queueing` checkbox. In the default (unchecked) case, the node behavior is unchanged. When the option is selected, the node toggles between the `open` and `queueing` states, with the queue being flushed each time the `open` state is entered.

The change is intended to be backward compatible, so that users who do not want the new feature will not need to upgrade. Please report bugs or issues here or on [GitHub](https://github.com/drmibell/node-red-contrib-queue-gate/issues).

Thanks to Simon Walters (@cymplecy) for [suggesting](https://github.com/drmibell/node-red-contrib-queue-gate/pull/7) and helping to implement this feature.