Administration

Overview

The Pendula infrastructure is designed to handle high volumes of experiences across all our customers. Many of the limits outlined below are configurable depending on the use case or requirements of your other systems of record or channel integrations. This article outlines the default limits for Pendula’s platform.

Pendula platform limits are subject to change and depend on the appropriate usage of our system. We encourage sensible limits when creating flows to prevent errors or misuse.

The rate at which Pendula processes experiences and/or messages are sent from a flow is a concept that is closely related to platform limits.

The overall rate of delivery for messages from a Pendula flow is determined by the composition of the flow.

In practice, this means that Pendula’s limits are often not determining the rate at which recipients are receiving your messages—more often than not, it is the origin of customer data or another integration that limits the rate at which experiences are processed.

As an example, the webhook trigger for a flow will accept up to 200 requests/second and will create an experience for each request.

After creation, experiences will wait in the Ingress Queue to enter the first node in the flow. The maximum queue size is 100,000 experiences.

The next action node in the example can then process experiences at a max rate of 200 req/sec (the same as the trigger). Some nodes (for example, outbound email) may process experiences at a much slower rate.

Once the flow rate of the experiences has been reduced, it cannot increase organically, unless there is another queuing point, and then experiences will be processed at the rate of the first action after the queuing point.

Not all queues have max queue sizes, only the ones documented by Pendula.

Core trigger & action limits