LinkedIn never tells you when someone declines your connection request. The only signal is indirect: the invitation disappears from your Sent list, but the person does not appear in your connections. To know for sure, you have to compare your Sent list against your connections over time.
What actually happens when someone declines
When a recipient taps "Ignore" on your invitation, three things happen quietly: the request leaves their inbox, it eventually leaves your Sent list, and no notification is sent to anyone. LinkedIn built it this way on purpose; declining would feel rude if the other side found out, so the platform hides it completely.
The same silence applies when an invitation expires after about six months without an answer. From your side of the fence, a decline and an expiry look identical: the request is simply gone.
How to check what happened to a specific request
- Open your Sent invitations. Go to linkedin.com/mynetwork/invitation-manager/sent/ and look for the person. If they are listed, the request is still pending. Nothing has happened yet.
- If they are not listed, search your connections. Open your connections list and search their name. If they appear, they accepted. Congratulations, this is the good outcome.
- If they are in neither list, check their profile button. Visit their profile. If the button says "Pending", your request is somehow still open. If it says "Connect" again, the request was declined, ignored, or expired.
What the profile button tells you
| Button on their profile | What it means for your request |
|---|---|
| Pending | Still waiting. They have not accepted or declined. |
| Message (and they are in your connections) | Accepted. You are connected. |
| Connect (after you already sent a request) | Declined, ignored, or expired. LinkedIn will not tell you which. |
Note the ambiguity in the last row. LinkedIn compresses three different outcomes into one visual state, and unless you wrote down when you sent the request, you cannot even distinguish "they said no" from "it timed out". This ambiguity is why serious outbound needs record-keeping.
Checking one person is easy. Checking a pipeline is not.
The three steps above take a minute for one prospect. If you send twenty to fifty requests a week as the LinkedIn step of your sequence, reconciling your Sent list against your connections becomes a real chore: you would need last week's list to compare against, and LinkedIn only ever shows you the current one. The decline signal is also the actionable one for a rep: a prospect who declined should move to email or phone in your cadence instead of sitting in "pending" forever. Teams that track this seriously keep a spreadsheet with prospect, date sent, and status, and update it weekly.
Frequently asked questions
Does LinkedIn notify you when someone declines your connection request?
No. LinkedIn never notifies the sender when a request is ignored or declined. The invitation just disappears from your Sent list without any message, which is a deliberate design choice to keep declining socially painless.
Can I send another request after someone declined?
Usually yes. Once the Connect button reappears on their profile you can technically re-invite them. Do it thoughtfully: add a note explaining why you want to connect, or engage with their posts first. Repeated unexplained requests to the same person can lead them to click "I don't know this person", which counts against your account.
What does it mean if my request is pending for months?
The person has neither accepted nor declined, which usually means they rarely check LinkedIn or they skimmed past your request. LinkedIn expires unanswered invitations after about six months. Withdrawing requests older than a month or two and re-targeting is generally more productive than waiting.
What is a normal accept rate for LinkedIn connection requests?
It varies too much with targeting to give one number honestly. Requests to people who know you or share real context with you are accepted far more often than cold requests, and a short personal note reliably outperforms a blank invitation. The useful move is to measure your own baseline for a few weeks and then test changes against it.