Why LinkedIn blocks some of your connection requests

If a contact in NavyPigeon shows a "Failed" LinkedIn status, the most common cause isn't a bug in your sequence or a bad profile URL — it's LinkedIn itself declining the invite. NavyPigeon can only ask LinkedIn to send a connection request; it can't override how many LinkedIn is willing to accept from your account in a given period.

The limit that trips people up

LinkedIn separately caps connection requests sent with a personalized note from requests sent without one. The note-included allowance is the tighter of the two — free and Basic accounts get a small number of these per month, and once an account is over it, LinkedIn rejects further note-included invites until the next period starts, even to profiles never contacted before.

NavyPigeon always sends a personalized message with a connection request — that's the point of a sequence step — so every LinkedIn send counts against this note-included allowance, not the more generous no-note limit some other tools rely on.

LinkedIn doesn't publish a single fixed number, and it can change without notice or vary by account standing and plan, so treat any specific figure — including "around five a month" for free accounts, which is what NavyPigeon's outreach provider documents today — as a guide rather than a guarantee.

Why it looks fine right up until it isn't

The cap resets on a rolling schedule, not per day, so a burst of sends that looks reasonable in one sitting can quietly use up an entire month's allowance. LinkedIn also doesn't warn in advance — the first sign is usually a rejected invite, which in NavyPigeon shows up as a failed send rather than a silent skip.

What NavyPigeon does when this happens

A blocked invite is marked "Failed" on the contact's LinkedIn status and recorded in activity history, so it stays visible instead of silently disappearing. It doesn't retry — retrying a blocked send just wastes the next slot — and it doesn't affect the rest of that contact's sequence or any other contact's requests.

Working within the limit

• Spread LinkedIn steps across more days rather than sending in bursts — the cap resets over time, not per project.
• Connect more than one LinkedIn account to a workspace if outreach volume needs it — each account has its own allowance.
• Consider a LinkedIn Premium, Sales Navigator, or Recruiter seat if connection volume is central to the workflow — paid tiers get a materially higher note-included allowance.
• Check activity history for the exact reason behind a failed request before assuming it's a limit — a small share of failures come from other causes, like an invite that's already pending.