# How to clear pending LinkedIn invites without hurting your account
> Find your sent LinkedIn connection requests, decide which ones are stale, and withdraw them in small batches so your invite pool stays healthy.
- HTML: https://getkinlead.com/cleaning-up-pending-linkedin-invitations
- Markdown: https://getkinlead.com/cleaning-up-pending-linkedin-invitations.md

**Short answer:** Open your sent invitations, withdraw requests that have gone unanswered for a few weeks, and do it in small batches. LinkedIn doesn't publish exact limits, but a large pool of ignored requests is a risk signal, so keep the pool small and watch for warnings.

## Why pending invites matter

When you send a connection request, it sits in a pending state until the person accepts, declines, or ignores it. Most people ignore. That is normal. The problem is what happens when ignored requests pile up for months.

LinkedIn does not publish a formula for how many pending invites are too many. It also does not say that a high pending count alone gets an account restricted. But the sent invitations tab is one of the few places where your outreach behavior is visible. A large pile of old requests suggests you are connecting with people who do not know you.

If your acceptance rate drops and you keep sending, you may see warnings, a temporary block on invites, or a request to verify you know the person's email. The exact trigger varies by account. Treat the pending pool as something to manage, not something to ignore.

A small pool is easier to review. You can see who has not replied, who viewed your profile, and which source sent the most ignored requests. That information is useful even if you never hit a warning.

**Account that ignores the sent tab**

- Hundreds of requests from last year still pending
- Sending new invites every day without checking acceptance
- Withdrawing everything in one sitting after a warning

**Account that keeps the pool small**

- Checks sent invitations once a week
- Withdraws old requests in small batches
- Slows down when LinkedIn shows a warning

> If someone has ignored a request for weeks, do not send another message. Withdraw the request and put the person back in your research list only if you find a new reason to connect.

## How to find your sent invitations

The list is not on your home feed. You need the sent tab inside invite management. The labels move around, but the path is the same on desktop.

If you have a long list, use the browser search to find a name you remember. That is faster than scrolling through years of requests.

1. **Open my network.** Click the My Network icon in the top navigation bar.
2. **Open manage invites.** On the network page, click Manage invite requests. It sits near the top of the page.
3. **Switch to sent.** The default view shows invites you received. Select Sent to see requests you have sent that are still waiting.
4. **Start with the oldest.** Scroll to the bottom or sort by date. The oldest requests are the ones most likely to be dead.

> The sent tab shows requests that are still pending. It does not show requests that were already accepted or declined. If a name is missing, the person already responded or the request expired.

## Decide which requests to withdraw

Do not withdraw every unanswered request on day one. Some people check LinkedIn once a week. A request that is a few days old may still get accepted.

Use age and context. A request to a warm contact from a shared group or a recent conversation deserves more time. A request to a cold prospect from a broad search can go sooner.

If you sent a note, the note can make the request feel less cold. But a note does not reset the clock. A request with a note that is over a month old and has no reply is still a request to withdraw.

| | Age of request | What to do | Why |
| --- | --- | --- | --- |
| Under 7 days | Leave it | The person may not have seen it yet. |
| 1 to 2 weeks | Leave it, but check context | Weekly users may still accept. |
| 2 to 4 weeks | Withdraw if there was no prior contact | The odds drop and the request starts to clutter your pool. |
| Over 4 weeks | Withdraw | This is old enough to be dead weight. |

> If the person viewed your profile after you sent the request, give it a little more time. A view is a weak signal, but it means the request was not completely ignored. If you sent a note and got no reply, that is not a reason to withdraw faster. The note did its job by giving context. The person may still accept later.

## Withdraw requests without tripping alarms

Withdrawing is an account action. Doing hundreds in a few minutes looks automated. LinkedIn does not publish how many withdrawals are safe, so you have to work within what your account allows.

Start with a small batch. Stop if the withdraw button stops working, if you get a security check, or if LinkedIn asks you to verify something. Those are signals to slow down.

If you have a large backlog, pick a time when you will not be tempted to rush. Do one pass in the morning and one in the afternoon. Close the tab between passes.

1. **Start with the oldest.** Open the sent list and work from the bottom up. The oldest requests are the safest to remove.
2. **Withdraw a small batch.** Do a handful, then close the tab and come back later. Do not try to clear a year of requests in one session.
3. **Spread a backlog over several days.** If you have a large pile, do a little each day instead of clearing it in one go.
4. **Record what you withdrew.** Keep a simple list of names and dates so you do not send the same person another request too soon.

> Do not withdraw and resend in the same minute. That looks like a loop. Wait until the person has had time to see a new request, or move on to a better target.

## Keep the pool small going forward

The cleanup is a one-time fix. The bigger fix is how you send requests. If you send to anyone who matches a broad keyword, the pending pool will refill. If you send to people who have a reason to accept, it stays small.

Use a simple rule: only send a request when you can name why that person would recognize you or your company. That reason can be a shared group, a comment they left on a competitor's post, a job posting, or a newsletter they wrote. If you cannot name it, do not send.

If you use a tool to send requests, set your daily invite limit lower than you think you need. The limit is there to protect the account, not to hit a target. A smaller number of well-chosen requests is easier to review and easier to defend.

- **you:** Saw your comment on Northwind's post about routing delays. We work on the same problem for 3PLs. Open to connecting?
- **them:** Sure. We are looking at this now.
- **draft:** Thanks. I'll send a short note tomorrow with the one question I'd ask first.

> Check your sent invitations once a week. It takes a few minutes. If you see a growing pile of old requests, stop sending new ones until you clear some. That is more useful than watching your acceptance rate after the fact.

```
Weekly invite check
1. Open sent invitations.
2. Withdraw requests older than 4 weeks with no prior contact.
3. Note any request that got a profile view in the last 7 days.
4. Pause new invites if the pending pool grew two weeks in a row.
5. Update your target list with one reason each person should accept.
```

## What to do if LinkedIn blocks your invites

If the invite button stops working or LinkedIn asks you to verify a phone number or email, stop sending. Do not open a second account or ask a teammate to send from theirs. That makes the problem harder to unwind.

Withdraw the oldest pending requests first. Then wait. Do not send another invite until the block clears and you have changed your targeting. If you go back to the same list, you will end up in the same place.

Look at the requests that were accepted and the ones that were ignored. If the ignored ones share a source, drop that source. If they share a job title or a company size, narrow the list.

1. **Pause all new invites.** Stop sending from every tool connected to the account, not just the browser tab.
2. **Clear the oldest requests.** Withdraw the requests that have been pending the longest. Do a small batch at a time.
3. **Check your acceptance rate.** Look at the requests that were accepted and the ones that were ignored. If the ignored ones share a source, drop that source.
4. **Change one thing.** Pick a narrower target list or a clearer reason to connect. Do not change your headline, photo, and targeting on the same day.

> A block usually means LinkedIn wants you to slow down and fix the input. Stop sending until it clears, then change your target list before you start again.

## Doing this with Kinlead

Kinlead withdraws stale pending invitations automatically to keep the pending pool from growing into a problem. Settings shows your pending invitations and acceptance rate with warnings, so you can see when targeting is drifting before LinkedIn pushes back.

If LinkedIn does push back on an account, Kinlead pauses invites on that account and emails you. It does not warm up accounts or guarantee that a restriction will not happen. It keeps sends inside the daily invite and message limits you set and inside a send window in the lead's time zone.

You can read more about [LinkedIn account safety](/features/linkedin-account-safety).

> Kinlead does not store your LinkedIn password. Outreach runs from your own account through a third-party LinkedIn provider.

## Related

- [Account safety features](https://getkinlead.com/features/linkedin-account-safety.md)
- [Campaigns and send windows](https://getkinlead.com/features/campaigns-and-send-windows.md)
- [Lead groups and scoring](https://getkinlead.com/features/lead-groups-and-scoring.md)

## Common questions

**Does withdrawing an invite notify the person?**

No. The request disappears from their pending list. They are not told that you withdrew it.

**Can I resend an invite after withdrawing it?**

Yes, but wait. If you resend too quickly, LinkedIn may treat it as spam. Send a new request only when you have a new reason to connect.

**How many pending invites are too many?**

LinkedIn does not publish a number. Keep the pool small enough that you can review it weekly and withdraw old requests before they pile up. If you see warnings or your acceptance rate drops, pause new invites.

**What if the person viewed my profile but did not accept?**

Give it a little more time. A view is a weak signal. If the request is over a month old and there was no conversation, withdraw it.

**Should I withdraw invites before or after a profile update?**

Do one change at a time. If you just changed your headline or photo, wait a few days before a big cleanup so you can tell what caused any warning.

[Create a Kinlead account](https://getkinlead.com/signup) or [book a call](https://getkinlead.com/demo) to talk through pricing and setup.
