Review flags and hold to launch

Review is exception handling. Clean rows are already in the send pool. You do not tick every person. Flagged people get a one-at-a-time card: fix or skip.

Same idea as Safety, with the actual flags and toasts. If you are still on the first launch path, see Launch your first campaign. Drafts are covered in Personalization.

When Hold to launch is enabled

You need all of:

1. At least one clean row (unflagged, not skipped)
2. A runnable sequence step: View profile, Follow, Like post, Comment on post, or Connection request (Message-only graphs cannot launch)
3. At least one sender
4. Remaining invite capacity

Disabled CTAs and toasts you may see:

• Add people to launch
• Blocked — campaigns need at least one eligible prospect before launch.
• Connect LinkedIn before launch
• Choose at least one sender before launch
• Invite cap reached for today or this week
• Daily cap reached. Approved prospects stay scheduled.
• Launch from review before pausing.

If the button is dead, match the toast to the list above before opening Sequence. Sequence issues (no runnable step, Message with no invite upstream) are covered in Build a LinkedIn and email sequence.

Flag table

Flag	What to do
Missing URL	Add a LinkedIn URL or skip
Duplicate	Same profile twice in this campaign; skip one
Invalid email	Fix or clear; blocks Email steps
On DNC list	Workspace suppression. Remove from DNC or skip. Do not force send.
AI draft pending / AI draft failed	Wait, or write the note yourself
Missing first name / company / role	Template uses {{first_name}}, {{company}}, or {{role}} and the field is empty. Fill the field or edit the note.
Over 300 characters	Connection notes cap at 300

Missing merge fields become empty strings in the rendered note, then show up as flags here. Fix the field once or edit the note for that person.

Skip vs restore

Skip excludes them from this campaign. It is not workspace do-not-contact. DNC comes from Inbox Not interested or Settings. See Handle replies so sequences stop.

Restore brings a skipped row back into this campaign’s pool. It does not clear workspace DNC.

Hold to launch

Hold for about 400ms. Releasing early cancels. The button says Hold to launch N.

On live campaigns, people added later launch from the Add people sheet or overview. Open Review only when new rows are flagged. The review table helper says: Fix fields or skip. Hold to launch sends everyone who is ready.

Nothing sends without that hold. See Safety.

Why nothing is sending after launch

Check these in order:

1. Daily cap or warm-up still ramping. Look at the live cap on the sender card under Senders (Gradual ramp up). Do not chase published "80-100 invites a day" figures; OmniReach caps below that on purpose. Details: connection request limits.
2. Campaign paused
3. Waiting for invite accept. Accepts can take hours to show (LinkedIn does not notify instantly). Sequences that wait on Accepted your invite? use days for that reason.
4. LinkedIn returned a limit and we rescheduled (Invite cap reached...)
5. Failed actions on /actions?status=failed. Retry, skip, or archive from the Actions ledger.

Pending OmniReach invites older than 21 days are withdrawn overnight so the pending pile does not look automated. Personal invites you sent outside OmniReach are left alone.

Details that affect invites

• A public /in/slug is not enough to invite. We retrieve the profile first. That counts toward the daily profile-visit budget, shared with View profile steps.
• Connection notes count against a tighter LinkedIn ceiling on free accounts. Connection request · no note is the quieter option on young accounts.
• Hitting LinkedIn’s invite ceiling reschedules the send. You see a toast, not a silent fail.

Build a LinkedIn and email sequence covers the canvas. Add the right people to a campaign covers the roster.