My LinkedIn replies aren't showing on the dashboard — what's happening?
If your dashboard is missing recent LinkedIn replies even though prospects are clearly replying on LinkedIn, the most likely cause is an upstream outage at our LinkedIn integration partner.
First, the important thing: every reply is still safely in your LinkedIn inbox — nothing is lost on LinkedIn's side. The gap is purely between our LinkedIn provider and WarmySender, NOT between you and your prospect.
How the signal flows:
Prospect replies on LinkedIn → LinkedIn delivers to our LinkedIn provider → our LinkedIn provider notifies us in real time → WarmySender records the reply on your dashboard.
When those real-time notifications stall, the inbound message still reaches us through a 30-minute polling fallback, but the things the notification normally triggers — marking the prospect as replied, the auto-stop-on-reply check, the Slack / n8n / Zapier reply alert, and the dashboard reply counter — only happen when the notification itself arrives. So during the outage you may see follow-ups continue on threads where the prospect has already replied.
What is ours to fix and what is theirs:
- Ours — recording the reply, dashboard counters, the Slack / n8n / Zapier alert, and auto-stop-on-reply. A health monitor checks every 15 minutes whether reply notifications have gone quiet and raises an internal alert the moment they have.
- Theirs — the actual delivery of the notification from LinkedIn through to us. When that delivery stalls, we escalate it with them directly.
What WarmySender does during the outage:
- The 15-minute health monitor raises a high-severity internal alert within one check of the outage starting.
- The 30-minute polling fallback keeps pulling inbound messages so we retain a complete record of what arrived. This is cover, not a fix.
- Once delivery is restored, we replay every message that arrived during the outage and re-run the steps that were missed. That retroactively marks your prospects as replied, applies auto-stop-on-reply, wakes any step that was waiting on a reply, and sends the missed Slack / n8n / Zapier alerts. The replay is safe to run more than once.
What you can do as a customer:
- Reassurance: replies are not lost. Open the actual LinkedIn inbox to read them while waiting.
- If you have time-sensitive threads, manually pause the affected campaigns until the dashboard catches up — this prevents follow-ups from going out on already-replied threads during the outage window.
- Once recovery completes (typically within an hour of delivery being restored and the replay running), your dashboard reply counters will reflect reality and stop-on-reply will have been applied retroactively.
- If you suspect this is happening to your workspace, contact support at [email protected] with a sample prospect URL and roughly when the reply came in; we can check the state of your accounts and confirm the recovery timeline.
No extra LinkedIn calls are made during detection or replay — account safety always wins. Our job during an outage like this is detection, covering the gap with the polling fallback, and replaying on recovery; restoring delivery itself sits with our integration partner, and we chase it with them.