In previous versions of this node, if the user set a limit on the queue size and that limit was reached, all incoming messages would be discarded until space became available. As a result, the queue would contain the oldest messages. In some cases it may be useful to have the opposite behaviour: a new message is added to the queue and the oldest message is dropped, so that the queue contains the most recent messages. The new version provides a "Keep newest messages" option (checkbox) to do this. By default, the node still keeps the oldest messages, so this change should not break any existing flows.
With this feature, it is possible to retain only the latest message and release it on demand. (See the example flow provided.) A recent forum discussion How to get value into switch suggested a need for this in capturing updates of the dashboard
Please report bugs or issues here or on GitHub.