Throttle

Throttle nodes limit how many times a user (or global scope) can pass through a specific point in the journey within a time period. This prevents notification fatigue and enforces rate limits.

​

Configuration

When a run hits a throttled node and the limit is reached, the node is skipped and execution continues to the next node. The message is not queued or delayed; it’s simply not sent.

​

Example

A throttle configured as “max 3 per 24 hours, per user” ensures that even if a journey is invoked 10 times for the same user in a day, only the first 3 send nodes downstream of the throttle will fire.

​

Global Throttle

Set the scope to Global instead of Per user to apply a single limit across all users. This is useful when you want to limit the total volume of a specific notification type, regardless of who receives it. For example, a global throttle of “max 1000 per hour” on a promotional journey ensures you don’t flood your email provider if a marketing event triggers thousands of invocations.

​

Combining with Other Nodes

Throttle nodes work well in combination with other logic:

• Throttle + Branch: Throttle first, then branch on priority. Only messages that pass the throttle are evaluated.
• Throttle + Delay: Place the throttle before a delay to prevent too many delayed messages from queuing up.

​

What’s Next