Who this is for: Recruiters and Admins who want a single reference for every hard limit, platform constraint, and plan gate in Sequences.
Why this matters
Sequences has limits at multiple levels — how many steps you can add, how long delays can be, how many characters a LinkedIn note can have, which features require which plan. Hitting any of these unexpectedly will either block a launch, error out a recipient, or show a greyed-out UI element with no obvious explanation. This article documents all of them in one place.
Sequence-level limits
Limit | Value | What happens if you exceed it |
Maximum steps per sequence | 50 steps | The Add Step button is disabled once you reach 50. You cannot add more steps until you remove one. |
Maximum delay between steps | 365 days | The delay input field does not accept values above 365. An inline validation message appears. |
Minimum delay | 1 day | The step executes after atleast 1 day after the previous step completes and the schedule window allows. |
Sequence name character limit | 120 characters | The input field stops accepting characters at 120. |
Per-channel content limits
Channel | Limit | Notes |
Social Connection Request note | 200 characters (hard cap) | This is the professional social platform's limit. Recruiterflow enforces it in the step editor. If personalisation tokens resolve to a note exceeding 200 characters for a specific recipient, that recipient errors out at this step. |
Social Message body | No Recruiterflow-imposed limit | Subject to the professional social platform's own message length limits. Very long messages may be truncated or rejected at the social platform level. |
SMS body | Depends on your SMS provider | Character limits vary by the VOIP plan and destination country. Standard SMS is 160 characters per segment; messages longer than this are sent as multi-part SMS and billed per segment. |
Email body | No hard limit in Recruiterflow | Emails that are too large to deliver (typically above ~25MB including attachments) will error with "email too large" at the delivery stage. |
Plan gating — what requires an AIRA Plan upgrade
The following features are available on the AIRA Plan only. On the Platform plan, these options are visible in the UI but appear greyed out with an upgrade prompt and a link to contact the Recruiterflow Sales team.
Feature | Platform Plan | AIRA Plan |
Social Connection Request steps | Greyed out | ✓ |
Social Message steps | Greyed out | ✓ |
Conditional Branching | Greyed out | ✓ |
Task steps, step-wise analytics, channel performance reports, and the daily channel usage summary are available on the Platform plan — no upgrade required.
LinkedIn daily sending limits
LinkedIn daily limits are set by Admins in Settings → Automation Settings → Social Limits and Visibility Configuration. These limits apply per sender, per channel, on a rolling 24-hour window. The system maximum cannot be exceeded regardless of what is configured.
Two Social limits are enforced independently:
Social Messages per day — applies to Social Message steps across all sequences
Social Connection Requests per day — applies to Social Connection Request steps across all sequences. Includes both requests with a note and requests without a note combined.
Other constraints worth knowing
Constraint | Detail |
Sequences cannot end on a branch | Both the Yes and No paths of any branch must contain at least one step. A sequence ending on an unresolved branch will fail validation and cannot launch. |
At least one sender required | A sequence cannot launch without at least one sender selected. |
At least one schedule required | A sequence cannot launch without a sending schedule selected. |
Structural edits locked after recipient progression | Once at least one recipient has reached a step, that step and all steps before it in the same route cannot be added, removed, or reordered. See Editing a Sequence After Launch. |
Task reminder custom date | Custom date selection is not available for task reminders in sequences. Only preset reminder options are supported. |
Deleting a branch after launch | Deleting a branch condition from a launched sequence requires typing DELETE to confirm. All steps in both the Yes and No paths of that branch are permanently removed. |