From bcdaa024e5f74d2ed904d6e42c69808e075d3b33 Mon Sep 17 00:00:00 2001 From: Nick Aguilar Date: Wed, 3 Dec 2025 14:44:55 -0800 Subject: [PATCH] describe mappings trigger conditions limits --- src/connections/destinations/actions.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/connections/destinations/actions.md b/src/connections/destinations/actions.md index e44f16eab6..fe5f89dc68 100644 --- a/src/connections/destinations/actions.md +++ b/src/connections/destinations/actions.md @@ -403,6 +403,9 @@ Explanation: > info "" > Self-service users can add a maximum of 2 conditions per Trigger. +> warning "" +> A general maximum of 250 conditions per Trigger is in place. This maximum depends on the character length of the conditions. Beyond this limit event delivery may encounter issues and a 'Action missing mapping or trigger' error may be thrown. + Mapping fields are case-sensitive. The following type filters and operators are available to help you build conditions: - **Event type** (`is`/`is not`). This allows you to filter by the [event types in the Segment Spec](/docs/connections/spec).