Your campaign still has people waiting, but the sending account cannot add another personalized invitation note. The next action depends on the tool's fallback: it may hold the invitation, or it may send the request without the text you wrote. Check that choice before the queue reaches the limit. A campaign marked active does not tell you which version a particular person received.
The note limit and the invitation are separate events
LinkedIn's help page said on November 2, 2026 that a Basic member can add a personalized message to three connection requests per month, with a 200-character limit per note. It says Premium members can add personalized notes without that monthly note limit, while connection-request limits still apply. Some vendor help pages quote five or even five to ten notes. Those numbers conflict with the current LinkedIn page. Use the warning shown in the sending account's own LinkedIn interface to decide whether a note is available; do not budget a campaign around a vendor's older count.
Running out of notes does not by itself prove that LinkedIn blocked every connection request. It means the planned request with that note cannot be assumed to go out as written. The tool must either change the outgoing content, hold the person, or fail the action. Which one happens is a product setting and a lead-level state question.
Sources: LinkedIn: personalize invitations to connect, Dripify: limited personalized invitation notes
Vendors make different fallback decisions
Expandi documents an ‘Allow send without connector message’ setting. When enabled and the account hits the note limit, it disregards the message configured in the campaign and sends a connection request without it. Distro exposes the choice in the campaign: ‘Send anyway’ without a note is its documented default; ‘Don't send’ holds the person. If the opening note contains the reason for contacting someone, the default changes the invitation materially.
Dripify describes another path. A running campaign with a note can stop when that note cannot be sent. Its July 2026 help page says the note field is disabled for free LinkedIn accounts in the current campaign editor, and recommends removing the note or making a separate campaign without it for an older running sequence. These are vendor descriptions, not results from the same account test. Read the control and the lead state in the version you actually use.
Sources: Expandi: LinkedIn settings, Distro: create a LinkedIn campaign, Dripify: limited personalized invitation notes
Choose whether a request without context is acceptable
A no-note request can be intentional. It is a different message decision from a personalized invitation, though, and a tool should not make it silently for your team. If the recipient would need the note to understand the contact, choose the hold option where available. If a no-note request still fits the purpose, record that choice before launch and review the later message shown after acceptance. Do not assume the note text moves into that later step.
For an active campaign, inspect the next few queued people before changing the setting. Record who is held, who already received a request, and which sender owns each pending action. Avoid re-enrolling held people simply to restart a queue: the pending-invitations guide covers how to verify invitation state, and the campaign-pause guide covers scheduled steps after a deliberate hold.
Verify the first affected invitation
Use a consenting colleague as a test contact. Before the step runs, save the campaign's note and fallback setting, the sender account, and the person's lead status. Afterward, inspect both the tool's event record and the native LinkedIn sent-invitations view. Confirm whether an invitation exists, whether it included the note, and whether the tool has another action queued for that person. A ‘note entered’ field or an active campaign badge is not delivery evidence.
If the tool says it sent a request but LinkedIn shows none, stop the test campaign and ask the vendor how it distinguishes a failed note from a failed invitation. If the person is held, check whether changing the fallback will resume that existing lead or require a separate action. This is a proposed acceptance test, not a claim that any listed vendor has passed it.
- Before: sender, note text, fallback choice, and lead's next scheduled action.
- After: native invitation status, note presence, tool event, and remaining queue state.
A fallback setting does not settle LinkedIn's policy
LinkedIn says it does not permit third-party software that scrapes, modifies, or automates activity on its website, and warns that accounts can be restricted. Omitting the note does not change that automation rule or the account-restriction risk. If that exposure is unacceptable, use LinkedIn's native invitation controls and have the account owner review each request. The tool check above answers what the queue did; it does not change the platform rule.