Platform limits

This article gathers the main platform limits in one place. If you run into an error while importing data, sending messages, or running scenarios, check whether you hit one of the limits described below.

Profiles and databases

Field formats and sizes

The platform expects specific value formats for each field type. For the full description, see the Acceptable formats and restrictions article:

Field	Limit
Email	RFC standard format
Phone	International format (E.123), no separators
Date	RFC 3339 (ISO 8601) with a time zone
Country	ISO 3166-1 alpha-2 code or the full name
Vendor	No more than 26 characters
IP	IPv4
String	We do not recommend storing more than 100 KB in a single field

Profile size

• The total data volume of a single profile in the database is up to 16 MB, including all metadata.
• We do not recommend storing more than 2 MB in the profile's additional fields in total.

Subscriptions

Each profile has a limit of 200 subscriptions, or up to 20 subscriptions per resource in one channel. For details, see the Profile article.

Templates and channels

Channel	Limit
Image gallery in the HTML editor	One image — up to 2 MB; formats: jpeg, jpg, png, gif
Email	Any file type as an attachment — up to 12 MB (changeable via the MTA_ATTACH_MAX_SIZE config parameter); see Email attachments
Notify	Up to 5 images with a total size of no more than 50 MB (JPG, PNG, GIF)
WhatsApp*	JPG/PNG image up to 5 MB, recommended size 640×640
SMS	70 characters in Cyrillic or 160 characters in Latin per message; exceeding the limit is billed as two SMS. A single Cyrillic character makes the whole message Cyrillic

You can set a limit on the number of SMS parts in the template — then overly long messages will not be sent at all.

info

Image size and format affect email loading speed and provider limits. We recommend compressing images before uploading them when preparing the HTML version.

API

• The RPC API processes no more than 2000 requests per second.
• There is a limit on the request body size — the platform returns an error when it is exceeded. Contact your platform administrator for the current value.

info

If you send a large batch of data (for example, a profile import or a field update), split your requests into chunks and control the request rate so you do not hit the 2000 requests/second limit.

Automation scenarios

• Cycle limit — by default, one cycle runs no more than 20 times. When the limit is reached, the profile's task stops with the Cycle limit of 20 has been reached error. The platform administrator can change this value. For details, see the Cycle processing in scenarios article.
• Cross-scenario protection — if a profile visited the same scenario more than 20 times through the "Go to scenario" node, further transitions are blocked.
• Triggers — no more than 10 triggers per scenario.
• Rate limiter in the API call node — a limit of requests per time interval is configured ("token bucket" algorithm); profiles that do not receive a token go back to the end of the queue.

Custom channels

Place for custom channel limits

The description of custom channel limits (queue limits, message size, pipeline processing rate) — to be clarified with developers and added.

Data volume and sending limits

• The number of profiles in the database and the number of sent messages depend on the account tariff. Contact your Altcraft manager for the current tariff values.

Place for tariff limits

Specific numbers by tariff (profiles in the database, messages per month) — to be added after clarification with the team.

caution

• *WhatsApp — a registered trademark of Meta Platforms, Inc.