Skip to content

Change journey step limit to 50 #8008

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

Merged
merged 1 commit into from
Oct 6, 2025
+2 −2
Merged

Change journey step limit to 50 #8008

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
4 changes: 2 additions & 2 deletions src/engage/journeys/v2/limits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ This page outlines product limitations for Event-Triggered (V2) Journeys.

| Name | Limit | Description |
| ------------------- | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Steps | 25 | Maximum number of steps per journey. |
| Steps | 50 | Maximum number of steps per journey. |
| Journey name | 73 characters | Maximum length for Journey names. Names must be unique. |
| Step name | 73 characters | Maximum length for step names. |
| Branch name | 73 characters | Maximum length for branch names within a split step. Branch names must be unique across the journey. |
Expand Down Expand Up @@ -72,4 +72,4 @@ This page outlines product limitations for Event-Triggered (V2) Journeys.
| HIPAA eligibility | [HIPAA-Eligible Services](https://www.twilio.com/content/dam/twilio-com/global/en/other/hipaa/pdf/HIPAA-Eligible-Services.pdf){:target="_blank"} |
| GDPR & BCR | See [Complying with the GDPR](/docs/privacy/complying-with-the-gdpr/) for more information. |

Segment complies with GDPR through Binding Corporate Rules (BCR). When a customer churns, BCR-initiated deletion removes the customer’s workspace and data. To request access to, correction of, or deletion of personal data, reach out to [Segment support](mailto:[email protected]).
Segment complies with GDPR through Binding Corporate Rules (BCR). When a customer churns, BCR-initiated deletion removes the customer’s workspace and data. To request access to, correction of, or deletion of personal data, reach out to [Segment support](mailto:[email protected]).
Loading