Configuration
| Field | Description |
|---|---|
| Max allowed | The maximum number of times a recipient can pass through this throttle within the period |
| Period | The time window for the limit (e.g., 1 hour, 24 hours, 7 days) |
| Scope | What the limit applies to: per user (keyed by user ID) or global (across all users) |
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.