Skip to main content

Queuing & Rate Limiting

System Queue​

Ziggy operates its own background queuing mechanism for all Flows. This ensures that the system is not overloaded with requests.

You should refer to Performance tuning for information on how to optimize your server configuration.

The only way to circumvent the system queue is when launching Flows from an external API call and specifying doNotQueue. However, this should not be abused in high volume situations as system overload protection is bypassed.

User Defined Queue (rate limiting)​

HubSpot : you do not need to rate limit protect when using HubSpot Blocks. These have in-built rate-limit protection.

It is often helpful to use a user defined queue to stay within API rate limits. You can define these in Ziggy from Global Settings.

Queue settings

Queues are applied globally and work across all your Flows.

Defining a Queue​

You can manage queues and assign rate limits for each queue by clicking on the Queue section in Global Settings.

Queue settings

Using a Queue from a Block​

You specify that a Block should use a Queue. This will then place that block into the queue when it executes.

Queue settings
  • Click in the Block header on the ? icon.
  • Select the Queues Tab
Queue settings
  • Choose (or remove) the queue from the dropdown.
  • If a queue is selected, you will see a red Q icon in the header, as shown above.

Monitoring​

You can access Queue stats from Queue menu bar. This updates every 2 seconds so will show near real-time values,

Queue monitor

You can press the icon in the Peak overflow column to reset the peak value after adjusting performance values.

Security & Performance​

Queues are never persisted to disk, they are retained in memory. As a result, you should be aware that queues with a large number of entries can impact memory usage, although it would usually require a large queue backlog to cause problems.