A Running badge says the campaign is enabled. It does not prove that a particular sender has an eligible lead, that the next message is due, or that LinkedIn accepted it. Open the first action you expected to send, note its scheduled time and status, and check whether that message is already in LinkedIn's Sent view before restarting anything. The next step depends on which of those states disagrees.
Find the first action that did not happen
Start with one affected prospect and the exact action: connection request, ordinary message, or InMail. Write down the sender, campaign, lead, expected send time, and current task status. Then look for that action in the sender's native LinkedIn Sent or pending record. An empty campaign chart cannot tell you whether the task is scheduled for later, failed inside the tool, or sent but not yet reflected in a dashboard.
GetSales, for example, separates Failed tasks from In Progress tasks with future scheduled times. Its help page says an In Progress message with a future time can be working as configured. If the tool shows Failed, open that task's reason rather than changing the whole campaign. These labels are GetSales behavior; find the equivalent queue and event log in your own product.
Sources: GetSales campaign troubleshooting
Use the size of the failure to choose where to look
If every lead under one sender stops, inspect that sender's connection and verification state. HeyReach distinguishes a connected sender that is Available but in no active campaign from one that is Not Connected, Not Synced, waiting for a PIN, or on an Inactive Seat. Available is therefore not evidence that a campaign is sending. Check the campaign state separately. A verification challenge or account restriction is a stop signal for the account owner, not an invitation to rotate senders around it.
If several campaigns share a sender and only one waits, inspect that campaign's own schedule, lead pool, pause state, and position in the sender's queue. GetSales documents that an out-of-schedule sender, wait node, daily cap, or higher-priority automation can defer tasks. A zero-send day can be an expected queue outcome. Record the next scheduled slot and verify it against the sender's timezone before editing limits.
Sources: HeyReach sender status definitions, GetSales campaign troubleshooting
When only one lead stalls, read the recipient state
A message after a connection request depends on the connection actually being accepted. GetSales says its Send Message task can queue or fail while an invitation is pending, depending on the node setup. It also pauses follow-ups after a reply by default. That is a different cause from a disconnected sender. Check the lead's connection, reply, exclusion, and failed-task reason before touching the campaign schedule.
Keep message type separate. LinkedIn's own help says a non-connection may need InMail credits and that a member's InMail preferences can prevent contact. An ordinary connection message, an InMail, and a vendor's sequence step do not share one eligibility rule. If a native LinkedIn send fails for the same account and message type, follow LinkedIn's troubleshooting path and preserve the exact error for its support team.
Sources: GetSales campaign troubleshooting, LinkedIn message troubleshooting
Retry only after reconciling what was sent
Before a retry, compare the tool event, the next scheduled task, and LinkedIn's native sent record for the affected lead. If the native message exists, do not restart the sequence. If the tool reports a specific failure and the native action is absent, fix that failure and use a documented task-level retry where available. GetSales describes Restart on This Node for certain failed tasks; that does not establish the same recovery behavior in another vendor. If the tool cannot show whether the action was attempted, pause that lead and ask support for the event trace.
OutreachGenie is built by our owner, LeanOrchestr. Its current pricing describes a free workspace with no product-side quota, and its product page shows campaign progress, pending work, and failures. A user-set daily cap can still defer a step, and LinkedIn's own limits and account restrictions still apply. The price or progress view does not prove that an action was sent or that automation is approved by LinkedIn.
Sources: GetSales campaign troubleshooting, OutreachGenie pricing, OutreachGenie product overview
Leave the account stopped when the platform state is unclear
LinkedIn says it prohibits third-party tools that scrape, modify, or automate activity on its website and warns that prohibited use can lead to account restriction. A vendor's Running badge cannot override an account warning, a verification challenge, or a failed native send. Preserve the task ID, sender status, expected time, and exact error, then resolve the account issue through the platform and vendor support paths before resuming.
For a campaign that is merely waiting, the useful outcome is a confirmed next scheduled action. For a failed lead, it is a known reason and a single reconciled retry. If neither can be established, keeping the affected work paused prevents a blind restart from becoming a second unwanted message.