Skip to main content

Troubleshooting: Connection requests not sending

Kate Korol avatar
Written by Kate Korol
Updated over 2 months ago

There are several common reasons why connection requests may not be sent in LinkedIn automation, and most of them can be resolved on your own. In this article, we’ll walk through the most typical cases.

All contacts have already passed the "Send connection request" step, or there are no contacts left in the segment

To check this, open the automation and find the "Send connection request" node. Look at the number next to "In progress" — if it’s "0", it means the queue is empty and all contacts have already moved past this step. In that case, just add a new set of contacts to the automation.

Automation is paused or not scheduled to run

- Make sure the automation is enabled. You can check this in the "Automations" tab - the toggle should be blue.

- Also, verify that the schedule allows the automation to run at the current time. Go to "Automations" => select your automation => click "..." => choose "Config",
or open the automation and click the settings icon in the top right corner.
Another possible reason: a mismatch between the automation schedule and the sender profile’s schedule. This article explains more about that.

LinkedIn profile issues or proxy problems

There could be several causes here - the LinkedIn account might be logged out, the proxy might be paused, or the server might be undergoing maintenance.

To check the profile status: go to "Sender Profiles" => in the LinkedIn tab, check the current status of the profile. You’ll find more info about specific errors and how to resolve them in this article.

If the profile shows as "Working", but tasks aren’t being completed and just keep rescheduling, there may be a server-side issue. In that case, please contact our support team.

Multiple sender profiles in the automation and contact distribution are uneven

If multiple sender profiles are connected but only one of them is actively sending connection requests, here are possible reasons:
- One sender may have completed its tasks faster than the others. To check this, go to the "Send connection request" node => click the number next to "In progress".


In the modal that opens, select a sender profile (1) to see how many tasks remain for it.


Learn more about how contacts are distributed between senders here.

- The sender profile was added after the contacts were already in the automation. In this case, the queue for the new profile wasn’t generated. To fix this, either add a new batch of contacts, which will be distributed across all active senders, or redistribute existing tasks manually. Here is how to edit an active automation.

Weekly LinkedIn connection limit reached

LinkedIn applies weekly limits on how many connection requests a profile can send. This limit is personalized for each account and depends on various factors, so it cannot be predicted exactly.

To check if the weekly limit has been reached, go to "Sender Profiles" => open the relevant profile - if you’ve hit the limit, there will be a message under the avatar. LinkedIn resets this limit every Monday, so you’ll just need to wait for it to refresh.

If none of these suggestions solved your issue, contact the Grinfi support team, and we’ll be happy to help you find a solution :)

Did this answer your question?