There are several reasons why an automation may stop sending connection requests. Most are related to schedule settings, campaign logic, or limits. Below is a checklist to help you quickly identify and resolve the issue on your own.
1. Schedule Conflicts or Paused Automation
The most common reason is that Grinfi detects it is currently "non-working hours."
Check automation status: In the Automations section, ensure the automation is active (the checkbox is blue).
Check schedule settings: Open the automation settings via the "..." button → Config.
If "Use Sender Profile's Schedule" is enabled: Go to the Sender Profiles section and check if the profile status is Out of Schedule (offline).
If the checkbox is disabled (custom schedule): Check if this schedule overlaps with the profile's own schedule.
🟡 Note: The Sender Profile's schedule always takes priority! Automations can run only within the profile's working hours. If the automation schedule does not align with the profile schedule (e.g., automation is set for the evening, but the profile turns off at 6:00 PM), tasks will not be executed.
2. "Bottlenecks" or Empty Queue
Requests will not be sent if contacts cannot reach the Send connection request node.
Check the queue (In progress):
Find the Send connection request node in your automation and check the value next to the In progress status. If it is "0", all contacts have either passed this stage or the segment is empty. To resume, simply add a new selection of contacts to this automation.
Check previous nodes: Review the steps placed before the request node. They may be causing delays.
Example: If the first node is Like post and the second is Send connection request, the request will not be scheduled/sent until the profile performs the "like". If the daily limit for Like post is lower than for Connection Request, the first node will throttle the second.
3. Low Volume of Requests
If requests are being sent but the number is significantly lower than expected, check if the Sender Profile is participating in multiple active automations simultaneously. The total daily limit is shared across all automations connected to that profile.
4. Reaching Limits
LinkedIn limits: The social network sets its own algorithmic limits on the number of requests you can send. This limit is individual and depends on many factors. If reached, a corresponding label will appear under the profile avatar in the Sender Profiles section.
🟢 Tip: If your profile regularly hits LinkedIn limits, please refer to our article: LinkedIn Connection Limits: How to Avoid and Remove Restrictions
Sender Profile limit: Check whether you have reached the daily limit set in your Grinfi profile settings.
5. Contact Distribution Conflict Between Multiple Senders
If multiple sender profiles are connected to the same automation but one of them is not sending requests, possible reasons include:
One profile finished tasks faster: Click on the value next to the In progress status in the request node, select the specific Sender Profile in the modal window, and see how many tasks remain specifically for them.
Profile was added too late: If you connected a new profile to an automation after contacts were added and distributed, a task queue for the new profile may not have been formed.
Solution: Add a new selection of contacts (which will be distributed among all profiles) or force a redistribution of existing tasks. See the article: Contact Distribution Across Sender Profiles and Restart Options in Automation
6. Technical Issues with Profile or Proxy
Check the current status in the Sender Profiles section:
If the status is Error/Issue (e.g., LinkedIn is Logged Out or Proxy Error) — restore the session or wait for the proxy to recover.
See the article: Sender profile statuses. Сommon errors & fixesIf the profile status is Working and none of the reasons above apply (but tasks are constantly being rescheduled), a platform update or routine maintenance is likely underway.
Solution: Wait up to 60 minutes. This is usually enough time for server processes to complete and operations to resume.