Start by identifying what exactly isn't happening — the causes and fixes differ depending on the symptom.
Jump to the section that matches your situation:
↓ Connection requests aren't being sent
↓ Messages aren't being sent
↓ Leads are stuck In Progress
Connection requests aren't being sent
The three most common causes:
Sender is Out of Schedule — tasks only fire during the sender's active schedule window. Check the status pill on the sender profile.
LinkedIn daily limit hit — look for a red dot on the Send Connection Request card or LinkedIn Limit Hit > 0 in the sender's KPI row. GetSales pauses for 5 hours then auto-resumes.
Sender not connected to LinkedIn — if the sender profile shows a red error status, the LinkedIn session has expired. Reconnect it and restart the failed tasks on the node.
For the full step-by-step checklist, see No Connections Sent — Step-by-Step Troubleshooting.
Messages aren't being sent
Check the sender schedule first
Messages — like all tasks — only fire during the sender's active hours. If the sender shows Out of Schedule, tasks are queued and will run at the next working window.
Go to Sender Profiles → LinkedIn tab → Schedule and confirm the active days and hours are correct. Also verify the sender's timezone setting — a wrong timezone shifts the entire schedule window.
Lead hasn't accepted the connection request yet
LinkedIn messages can only be sent to 1st-degree connections. If the connection request is still pending, the Send Message task will either queue or fail depending on your node setup.
How to check: Open the node modal on the Send Message node and look at the task status. A Failed status with an error like "not connected" confirms this is the cause.
Fix: Add a delay node between the Send Connection Request and Send Message nodes to give leads time to accept. A 3–5 day delay is typical.
Lead replied and paused the automation
By default, GetSales pauses all follow-up messages when a lead replies. These leads stay In Progress on the message node indefinitely.
How to find them: Click In Progress on the Segment node → filter CRM by Pipeline Stage = Replied.
To have messages send regardless of replies, enable "Send always, even if contact replied" on the Send Message node.
Message node shows Failed tasks
Click the Failed counter on the Send Message node to open the task modal. The error message tells you the exact cause. Common ones:
Error | Fix |
Not connected to lead | Wait for connection acceptance, then Restart on This Node. |
Sender not linked to LinkedIn | Reconnect the sender profile, then Restart on This Node. |
Lead blocked the sender | Cancel these leads — messaging is not possible. |
Missing email address | Update the contact with a valid email via CSV, then Restart on This Node. |
Tasks are scheduled for later
If the node shows In Progress with no Failed tasks, the messages may simply be queued for a future slot. Click the In Progress counter and check the scheduled date and time — if it's in the future, the automation is working normally.
Email messages not sending
If the stuck node is a Send Email node specifically, also check:
The mailbox is connected and active on the sender profile (Email tab → connection status).
The lead has an email address — leads without one will fail silently on email nodes unless a fallback is configured.
Leads are stuck In Progress
If leads are sitting In Progress without progressing to the next node, see Stuck Leads: Why Leads Stay "In Progress" and How to Fix Them — covers reply detection, task scheduling, and free account connection limits.
Still not resolved?
Contact support with a screenshot of the node modal showing the task status and error message — that gives us everything needed to investigate quickly.
Related articles