Overview
The Pendula infrastructure which the Lumary Engagement Console is built on 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
Core triggers and actions are the nodes that are be used to create flows on the Experience & Workflow Studio builder canvas.
Builder node limits are per tenant.
| Throughput limits | Max request size | Daily limit | |
| Webhook trigger | 200 req/s | 250KiB | None |
| Make a web request action | < 200 req/s | 250KiB | None |
Ingress queue limits
The ingress queue contains experiences waiting to enter the first action in a flow.
Ingress queue limits are per flow.
| Dequeue limits | Max queue size | Daily limit | |
| Ingress queue | 200 req/s | 100,000 | None |
Messaging channel limits
Pendula supports a number of channels managed through the Engagement Hub. Each messaging channel has its own specific throughput and size limits. The ones detailed below are Pendula’s default platform limits, contact us to discuss your specific requirements.
Messaging channel limits are per tenant.
| Throughput limits | Size limits | Daily limit | |
| SMS | 10 messages (1) per second | SMS segment limit: 160 characters with GSM-7 encoding or 70 characters with UCS-2 encoding Total limit: 6 segments |
None |
| 14 emails per second | Email body limit: 250KiB Email subject limit: 255 characters (2) Total limit (body plus attachments): 10MiB |
50,000 | |
| WhatsApp (Early Access) | 80 messages per second | Message body limit: 250KiB | Business phone numbers are initially limited to 250 business-initiated conversations in a rolling 24-hour window |
- Messages may be multiple segments per message. See this article for more details.
- Email subject lines over 255 characters will not fail to send, but many email clients (including MS Outlook) do not accept email subject lines beyond this number. Best practice is to keep subject lines under 50 characters to avoid truncation in your recipient’s inbox.
Customer Data Suite limits
Early Access
The Customer Data Suite allows Pendula users to upload their own data to tables that can be used to trigger Pendula flows.
The following limits are per table.
| Max | |
| Number of rows | 500,000 |
| Object / field label length | 255 characters |
The following limits are per cell / field / value (e.g. the value of the “first name” column in any row)
| Value | |
| String length max | 64k (65, 535 characters) |
| Integer range | -9,223,372,036,854,770,000 to +9,223,372,036,854,770,000 |
| Decimal places max | 15 decimal digits |
Integration limits
Integrations to any external data source, including CRMs, billing systems, event-driven data sources (Power Ups), and other customer data sources are managed through the Integrations Hub.
Pendula does not throttle or control API usage for external systems. It is up to you to plan and manage your campaigns according to the API allowances of your chosen integration.
AWS Kinesis
The following limits are per flow.
| Throughput limits | Max payload size | Daily limit | |
| Event Triggers | Refer to AWS Kinesis Limits & Pendula Ingress Queue Limits | Refer to AWS Kinesis Limits | Refer to AWS Kinesis Limits |
| Activity Sync | Refer to AWS Kinesis Limits | 256 KB | Refer to AWS Kinesis Limits |