Skip to main content
Try the button first. Why isn’t this sending? on the sequence top bar (and on any sender’s page) runs the whole diagnosis below in a second and gives you one reason plus what to do about it. The checklist here is for understanding the answer.You may not even need to ask: a sequence that quietly stops raises a stall alert on its own.
Start by working out what exactly isn’t happening. The causes and fixes differ depending on the symptom. Jump to the section that matches your situation:

​
Nothing is being sent at all

Check these in order:
  1. Is the sequence active? Draft and paused sequences don’t send. A throttled badge means the sequence is being slowed down; hover it to see why.
  2. Are the pool’s senders connected? Open Senders. Any sender showing Re-login needed, Error or Paused holds its actions. See Sender Statuses and Errors.
  3. Is it inside working hours? Senders only work inside their schedule, in their own timezone. The default is Monday–Friday, 09:00–18:00. See Sender’s Schedule Explained.
  4. Has the daily cap been reached? Open the sender’s Budgets tab. If Used + Reserved = Cap, the sender is done for today.
  5. Is anything queued? Open the sender’s Overview tab and look at Upcoming actions. If there are queued actions with future times, everything is working; they’re just scheduled for later.
  6. Are there any leads left? A running dry notice on the sender means fewer than two days of new leads. Enrol more, or add an auto-enrol rule.
Tip: Newly enrolled leads are planned into the next planning run, which happens nightly. To plan them into today’s remaining hours, click Plan now on the sender’s Overview tab.

​
Invitations aren’t being sent

  • Weekly limit reached. Each sender can send 150 invitations a week (weeks start Monday). Check Weekly invitations on the Budgets tab.
  • “Invites blocked until…” badge. LinkedIn said it “cannot resend yet”. Invitations resume next Monday.
  • Low warm-up level. A level 0 sender only sends 4 invitations a day. See Warm-Up Best Practices.
  • Health between 50 and 69. All caps are cut to 60%.

​
Messages aren’t being sent

  • The lead isn’t connected yet. LinkedIn messages only go to 1st-degree connections. Make sure the message comes after Send invitation → Wait for connection, on the connected branch.
  • The lead replied — possibly to a different sender. With the default reply scope, a reply to any sender on any channel stops every sequence that lead is in. An email reply stopping the LinkedIn follow-up is working as designed. To keep one step going regardless, turn on Send even after the lead replied on that step.
  • A manual step, a call task or an AI draft is waiting. Steps set to Manual mode, call tasks and AI drafts all wait for a teammate. Check the Tasks tab.
  • The lead is waiting for data. With wait for enrichment or hold for AI review on, a lead waits before its first step. Check the lead page.
  • The voice clip is missing. A voice-note step skips for any sender that hasn’t recorded a clip.

​
Leads aren’t moving to the next step

Open the lead and look at their enrollment’s status: See Enrollment Statuses: What Each One Means.

​
Q: How can I get a direct answer without checking everything?

Click Why isn’t this sending? on the sequence or the sender. Or ask Claude “why isn’t anything sending?” through the connector — it runs the same diagnosis and explains the cause in plain language.

​
Still not resolved?

Contact support with the sequence name, the affected sender, and a screenshot of the sender’s Budgets tab and Events tab. That gives us everything we need to look into it quickly.