Work through the steps below in order. Each step tells you what to look for and what to do if you find the problem — stop as soon as you find your answer.

Go to Sender Profiles and select the sender. Look at the status pill in the header.

If it shows a red error state (login error, proxy error, access issue) → the LinkedIn session is broken. Reconnect the profile or open the session via Open in Cloud Browser to resolve the checkpoint. See Sender Profile Statuses and Errors for each error type and its fix.

If it shows "Out of Schedule" (orange) → the sender is idle because the current time is outside its working window. The header shows today's window inline (e.g. Today, 9:00 to 18:00 UTC). Go to Manage → Update Schedule to expand it.

If it shows "Stopped" (orange) → the sender was manually paused or stopped by billing. Resume it from the same Manage menu.

If it shows "Working" → the sender is connected and active. Continue to Step 2.

Still on the LinkedIn tab, look at the Send Connection Request activity card near the top. It shows Total scheduled.

If Total scheduled = 0 → the sender has no connection tasks queued at all. Skip to Step 5 to find out why.

If Total scheduled > 0 → tasks exist. The sender has work to do. Continue to Step 3.

Scroll down to the Daily Activity vs LinkedIn Limits chart on the LinkedIn tab. Look for a red dot on the Send Connection Request activity card at the top, and check the LinkedIn Limit Hit KPI in the row below the chart.

If the red dot is showing, or LinkedIn Limit Hit > 0 → LinkedIn has paused connection requests for this sender. GetSales automatically resumes after 5 hours. While waiting, avoid sending manual requests from LinkedIn — they count against the same cap.

To reduce how often this happens, lower the sender's Target daily limit so the weekly total stays within LinkedIn's ceiling. See LinkedIn Connection Limit Reached Explained for the full recovery steps.

If no red dot and LinkedIn Limit Hit = 0 → no LinkedIn-side block. Continue to Step 4.

Scroll further down to Auto Tasks & Daily Limits and find the Send Connection Request row. Compare Daily limit (today's actual cap) with Target daily limit (your goal).

You can also cross-check from the activity card at the top of the tab: Done today: X of Y — the Y is today's effective daily limit.

If Daily limit is much lower than Target → Auto-warmup is still ramping the account. This is normal and intentional — the system raises limits gradually to keep the account safe. The Warmup Level card at the top of the tab shows your current tier and how many more monthly actions are needed to reach the next one.

No action needed. See Auto-warmup Guide if you want to understand the timeline or check your tier.

If Daily limit = 0 → Auto-warmup may be holding limits due to an Account Health issue. Click View details on the Account Health card and check for orange warnings.

If Daily limit matches Target and Done today is counting up → connection requests are sending normally. If the volume feels lower than expected, that's a pacing question rather than a problem — see Auto-warmup Guide for how to safely raise your Target daily limit and progress through Warmup Levels faster.

In a multi-sender automation, leads are distributed across senders. The sender you're investigating may simply have none assigned to it.

Go to the CRM, filter contacts by the automation, and then filter by this specific sender profile. Or click the counter on the Send Connection node and filter by sender.

If no leads are assigned to this sender → leads went to other senders. This is expected if the sender was added to the automation after leads had already been distributed — late-added senders only pick up new leads from that point forward. Add fresh leads to the automation to start filling this sender's queue.

If leads are assigned → continue to Step 6.

Open the automation and scan the node counters. Leads may be sitting in a Wait, Condition, Check Reply, or Send Message node before they reach Send Connection.

If leads are shown as "In Progress" on an upstream node → those leads haven't reached Send Connection yet. They're not lost — just queued earlier in the flow. If a Wait node seems longer than expected, check its configured duration or whether reply detection rerouted those leads to a different branch.

If all leads have passed through upstream nodes and are at Send Connection → continue to Step 7.

GetSales silently skips leads who are already 1st-degree connections — no error is shown.

In the CRM, filter the contacts in this automation by LinkedIn connection status = "Connected."

If most leads are already connected → the node has nothing to send. Add a filter at the automation entry to exclude already-connected leads, or switch to a fresh segment.

If leads are not connected → continue to Step 8.

A few less common situations to rule out:

If you've worked through all steps and connections still aren't sending, reach out via chat with the automation name and sender profile — support can inspect the task queue directly.

Also useful to share: a screenshot of the Daily Activity chart and the Done today / Total scheduled values from the activity card.