No, but I am thinking about how to clarify the documentation. Every control message (command) has three attributes: a name, a default value (payload), and an action it produces. The message you are discussing is named triggerCmd. Its default value is "trigger", and the action it causes is dequeue. I can see how even someone very familiar with the node could become confused. In this case, the error is in how the node was configured in the edit dialog. If the triggerCmd were defined as "dequeue", the node would work as @krambriw expects.
BTW, when the node was being developed, I was reminded that several existing nodes and flows for queueing messages use a command called trigger to release the next message, and that the term "dequeue" might be too technical for the average user. It seems that no good deed goes unpunished.
