The Throttle Node allows a workflow to branch based upon the amount of time that has passed since the last time the Throttle Node was executed. In the simple and common use case, it can be used to throttle a workflow to only run a certain number of times per time period.
There are two parts to the configuration of this node …
The Throttle Node is configured by specifying the rate of executions of the node per time period. The available time periods are “Second”, “Minute”, “Hour”, and “Day”, and the rate is allowed to be anything above 0 and below 10 times per second.
If enough time has passed between the last un-throttled execution of the Throttle Node, the right (un-throttled) route out of the node is taken. If not enough time has passed (i.e., the number of executions has exceeded to specified rate), the left (throttled) route out of the node is taken.
The Throttle Node also has an optional field named
Throttle Identifier. This field is a string template and can be used to make a single Throttle Node function as the equivalent of multiple throttle checks.
For example, if multiple Devices can trigger a workflow and pass through this Throttle Node, you can have the throttle identifier be the triggering device ID. That way the on throttle will work on a per-device basis, instead of on a global workflow basis.
In the above example, the workflow will follow the right route out of the Throttle Node and proceed to send a device command only if it has been at least a minute since the last time the workflow went down that route. If it has been less than a minute, the workflow follows the left route - and since there is no node attached to the left route, the execution of the flow stops.
This node does not have any node specific errors.