Skip to content

[actions] Describe limits with defining trigger conditions #8165

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nick-Ag wants to merge 1 commit into from
Closed

[actions] Describe limits with defining trigger conditions #8165

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions src/connections/destinations/actions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Expand Down