FAQ & Troubleshooting

By Alex Mishyn

• 7 articles

Why Are Connection Requests Not Sending: Troubleshooting

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 profiles: Statuses Overview & Troubleshooting] - If 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.

Last updated on Jul 02, 2026

Why Are Messages Not Sending: Troubleshooting

Most reasons why messages are delayed, stuck, or not sent in Grinfi can be quickly identified and resolved on your own. Below is a troubleshooting checklist: from automated sequences to manual messages in the messenger. 1. Messages in Automation: Pauses or Schedule Conflicts 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" checkbox 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. Contacts Stuck Due to a Reply (Paused after reply) If some contacts are stuck in the In progress status at a message node and haven't moved for a long time, they likely have the Paused after reply status. How it works: This is a built-in safety mechanism to prevent unwanted spam. If a contact sends you a reply while they are in an active automation, Grinfi will stop sending them any new messages. 🟡 Note: Other technical nodes in the automation (e.g., Time delay or Like post) will continue to execute, but the contact will stop at the message node and wait for your manual approval. (Exception: if the Send always checkbox is enabled on the message node, the message will be sent regardless of the pause status). How to unpause a contact Unpausing is done manually for each contact: 1. Go to the Manual tasks section. 2. In the Automation filter, select the relevant automation. 3. Find the contact, click on them, and then click the Automation paused after reply button. 4. Select Unpause automations. 3. Tasks in the Auto Tasks Menu Are Constantly Rescheduled If it is time for a message to be sent, but the task is cyclically rescheduled for a later time, check the current profile 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 profiles: Statuses Overview & Troubleshooting] - If 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. 4. Manual Messages Are Not Sending (Messenger / Unibox) If you send a message manually via the Grinfi messenger, but it remains in a permanent Loading state Possible reasons: - Profile is out of schedule: The message is waiting in the queue and will be sent as soon as the profile's working hours begin. - Temporary proxy connection loss: If the profile is active but the message won't send, this indicates a temporary proxy downtime or slow connection. Wait and check again in 5 minutes, 30 minutes, or up to 1 hour. If the message is still not sent, contact support. 🟡 Note: If a message is stuck in "Loading" and you decide not to wait but send it directly from your LinkedIn profile instead, be sure to cancel the message in Grinfi first. Otherwise, as soon as the proxy recovers or working hours begin, the system will process the request, and your contact will receive the same message twice. 5. Message History Is Not Syncing in the Messenger If a profile received a message on LinkedIn, but it does not appear in Grinfi: - For direct messages: These sync almost instantly (up to 5 minutes maximum), provided the profile is active. If the history hasn't updated, it is likely a temporary proxy delay (wait for the proxy connection to be restored). - For InMail messages: These have a longer sync cycle. InMail history updates every 2 hours.

Last updated on Jul 02, 2026

Sender profiles: Statuses Overview & Troubleshooting

In the Sender Profiles section, under your account name, you may see different profile statuses. In this article, we'll explain what each status means, what technical issues may occur, and how to resolve them quickly and correctly. Main Sender Profile Statuses - Working 🟩 (Green indicator) - the profile is in an active phase and operating correctly. - Initializing 🟩 (Green indicator) - the system is synchronizing data and preparing the profile for work. This typically appears during the initial connection to Grinfi or if data hasn't been updated for a long time. This process can take up to several hours. - Out of Schedule 🟨 (Yellow indicator) - the profile is temporarily paused according to your schedule and is currently offline. Learn more in the article: [Sender Profile Work Schedule]. - Stopped 🟨 (Yellow indicator) - the profile has been stopped. This could be done manually by the user, or automatically by the platform due to limitations (e.g., exceeding the number of available sender profiles or an expired subscription). To resume, click the Run button. - Error / Issue 🟥 (Red indicator) - the profile has stopped due to technical issues. Solutions are described below. Common Errors and Solutions 1. Error: "LinkedIn is Logged Out" This error means the system has lost the connection to your LinkedIn profile and it needs to be restored manually. Solution: 1. Under your sender profile name, click the Log back into LinkedIn button. 2. A Cloud Browser window will open. Log in to your LinkedIn account (enter your credentials). 3. After a successful login, click I have logged in. The system will start verifying your connection. 4. If the verification is finished and you are definitely logged in, but the error status remains, click the three dots icon (...) next to the "Log back into LinkedIn" button and select I'm logged in - Run profile. 2. Error: "Something went wrong" If you see this status, it most likely means a system update or routine maintenance is currently being deployed on the platform. Solution: Such work usually takes up to 60 minutes. Please wait and try again, or check the profile status later. If more than an hour has passed and the error persists, please contact our support team for a detailed investigation. 3. Proxy Errors ("Proxy Error", "Curl", "IP", "we are fixing it", "[]") All errors with these names indicate that your proxy server has temporarily lost connection. What you should know about downtime: Any proxy server can experience temporary unavailability (downtime). This is a completely normal occurrence in network infrastructure. Such interruptions can last from a few minutes to several hours in case of provider-level issues. Solution: - Automatic monitoring: Grinfi uses an algorithm that automatically and regularly scans the problematic proxy. As soon as the connection stabilizes, the system will resume operation on its own. If the algorithm determines after a series of checks that the address is permanently unavailable, it will automatically replace it with a new one. 🟡 Note: The automatic replacement algorithm only applies to proxies provided by Grinfi. - For Custom Proxies: If you are using a third-party proxy and the algorithm detects unavailability for more than a few hours, contact your proxy provider's technical support. If the proxy is no longer working, request a replacement and reconnect it (click Manage → Update proxy for the selected sender profile). - Manual replacement: If you cannot wait for automatic recovery or a provider response, you can force a proxy change by clicking Manage → Update proxy. 🟡 Note: We recommend manual proxy changes only as a last resort! A new IP address is a direct trigger for LinkedIn's security algorithms. Changing IPs too frequently may lead to temporary restrictions or mandatory ID verification for your profile.

Last updated on Jul 02, 2026

CRM & Imports: Troubleshooting, Logic, and Management Rules

This section contains answers to common questions regarding lead uploading, data enrichment, and managing your contact database within the Grinfi system. How does contact data enrichment work? When a new contact enters Grinfi, the platform checks for its presence in our internal database: - Instant enrichment: If the contact is already in Grinfi's internal database, enrichment happens instantly — the system immediately pulls all available information. 🟡 Note: Since the data is pulled from the internal database, some information may be outdated. - General queue: If the contact cannot be found in the database, it is placed in the enrichment queue. - Advanced Enrichment node in automations: In the automation builder, you can add an Advanced Enrichment step. This node instantly triggers enrichment for contacts that pass through it, ignoring the default logic. This allows you to obtain the most up-to-date data while a campaign is running. You can find a detailed description of the Advanced Enrichment feature here: [Advanced Enrichment: How to Use]. - Process speed: Depending on the general queue and data volume, the enrichment process can take anywhere from a few hours to a few days. 🟡 Note: You do not need to wait for enrichment to complete. You can add contacts to an automation immediately. The system will hold them at the segmentation level and automatically launch them into the sequence once enrichment is finished. I have a Sales Navigator subscription, but it’s not showing up in Grinfi. What should I do? Typically, Grinfi detects a Sales Navigator (SN) premium subscription within 4 hours after connecting a profile or purchasing the plan. Sometimes LinkedIn delays sending this information if the subscription was purchased but hasn't been used yet. Solution: Log into your Sales Navigator on LinkedIn and perform any search. This demonstrates activity and forces LinkedIn's algorithms to update the profile status. If more than 8 hours have passed and Grinfi still hasn't detected your SN, contact support, and we will sync the data manually. There were more contacts in my search/CSV than were imported. Why? By default, the platform only uploads new, unique contacts. Any contacts already present in your Grinfi CRM (uploaded previously) are automatically filtered out and assigned the duplicates status. You can verify the exact number of uploaded contacts and duplicates in the Imports tab. Why does a CSV import show an "Error" status? The most common reason is using incorrect text encoding within the CSV file itself. Solution: Upload your CSV file to Google Drive → open it via Google Sheets → click File → Download → select .csv format. Then, upload this new file to Grinfi. I can’t start an import / Import is running very slowly Import speed depends on the source: CSV processing usually takes from 5 minutes to 3 hours, while Sales Navigator imports can take several hours due to LinkedIn limits. If the import isnєt collecting contacts or has stopped, check the following: 1. Profile status: Ensure your profile is active and not in an error state (see the article [Sender profiles: Statuses Overview & Troubleshooting]. 2. Working hours: Check the schedule settings for your sender profile. It might currently be paused according to its schedule. 3. Daily limits: Check if the profile has reached its daily import limit (found in the Sender Profiles tab). For Basic search: 1 search page = 10 imported contacts. For Sales Navigator: 1 search page = 25 imported contacts. Contact Management: Basic Principles To effectively manage your contact database in Grinfi, keep the following rules in mind: - Lists: Every imported contact is stored in a specific list. A contact cannot be in multiple lists simultaneously, but you can freely move contacts between them. - Tags: Unlike lists, a contact can have multiple tags. There are no limits on the number of tags assigned. - Working with automations: - The same contact can be added to several different automations at the same time. - If a contact replies to your message, all automations they are currently in will automatically pause. 🟡 Note: If the Send always checkbox is enabled in a message node's settings, the message will be sent even to contacts in a paused status. - A contact cannot be added to the same automation twice; the platform will ignore this action (exception: using the [Setting up "Rotate Sender Profiles" function], which allows a profile to re-enter the sequence).

Last updated on Jul 02, 2026

Connecting a LinkedIn Profile to Grinfi: Troubleshooting Guide

Connecting a LinkedIn profile to Grinfi is done step by step via the cloud browser. If you encounter any issues during the process, first identify the step where the error occurred. This will help you find a solution faster. Below you'll find detailed instructions for resolving common problems. Difficulties Opening the Cloud Browser Only one cloud browser session can be active within a workspace at a time. If you see the error "Failed to connect to Cloud Browser" or "You have reached the maximum number of simultaneously running cloud browsers" during startup, follow these steps: - Check your tabs: Make sure the cloud browser isn't accidentally left open in other tabs or browser windows. - Check team activity: Confirm whether other users in your workspace are currently using the cloud browser. - Close active sessions: Terminate all other cloud browser sessions and try connecting again. Alternative solution: If you cannot wait, complete authorization via the GoLogin browser - this method does not have limitations on the number of simultaneous sessions. You can find profile connection instructions in the article: [How to connect LinkedIn Account to Grinfi]. Unable to Set Up a Proxy Error when connecting your own proxy If you have selected your own proxy but the system does not allow you to proceed to the next step, the proxy server is likely experiencing temporary downtime. This is a normal occurrence for most providers. Solution: Wait 5 minutes to 1 hour and try again. If the connection still doesn't work, contact your proxy provider to test or replace the address. Alternatively, you can always use Grinfi's built-in proxy. Error "Something went wrong" This error usually indicates an inactive session token for your Grinfi account or temporary maintenance on the platform. Solution: First, sign out of your Grinfi account (click Log Out), clear your browser cache, and log in again. This will force a token refresh. If re-authorization does not help, we are likely deploying a platform update or performing scheduled maintenance at that moment. Such work usually takes up to 30-40 minutes. Please wait and try again. If the problem persists, contact support. "Error: Proxy Error. Request timeout after ___ms" This means the proxy lost connection exactly at the moment the browser was opening. Solution: Click the Change Proxy button to assign a new IP address and try opening the cloud browser again. If the problem continues, try changing the proxy several times. Unable to Pass LinkedIn Captcha During Login Captcha issues most often arise due to technical flaws in the LinkedIn interface. Captcha window is too small The LinkedIn interface sometimes displays images so small they are difficult to see. Since this is a technical issue on LinkedIn's side, it is impossible to enlarge the window — try to pass the verification as is. Infinite Captcha Loop If the LinkedIn algorithm decides you entered the captcha incorrectly the first time, it may send you into an infinite loop of verifications. - Step 1 (Pause): Stop connection attempts and try again in 24 hours. Usually, LinkedIn "resets" the data after a day. - Step 2 (Reset Connection): Click the Start over button in Grinfi and begin the authorization process from scratch. This will create a new digital fingerprint and help break the captcha loop. Error "Something went wrong" at the Final Stage An update or scheduled maintenance is likely being deployed on the server at this moment. Solution: Try again in 30-40 minutes. Your progress will not be lost — open the cloud browser and click I have logged in. Hotkeys Not Working in Cloud Browser If hotkeys are not working, it is usually related to your local browser's security restrictions or a conflict with extensions. Step 1: Grant browser permission Your browser (e.g., Google Chrome) must allow clipboard access for Grinfi. 1. In the browser address bar (where the website URL is shown), click the Settings icon. 2. Find the Clipboard item and set it to Allow. 3. Refresh the page to activate the changes. Step 2: Check for conflicting extensions Some browser extensions that affect text processing or translation can block hotkeys in the cloud browser (most commonly services like Grammarly, Google Translate, LanguageTool, etc). Solution: Temporarily disable or remove these extensions. If you prefer not to disable them, use alternative actions (e.g., copy-paste via right-click). Issues Connecting via GoLogin Session is not transferred to the profile ("User not found" error) Solution: Check that the email used in GoLogin is correct (you can find it in the top-right corner of the GoLogin browser → Menu). Grinfi session is not visible in GoLogin Solution: Force refresh the session list. Press Cmd + R (Mac) or F5 / Ctrl + R (Windows). You can also click All Profiles in the top left corner of the GoLogin interface. Unable to start GoLogin session - Browser update: Check for critical updates for the GoLogin app itself. Close the program completely, reopen it, and install updates. - Proxy temporarily unavailable: Wait 5 minutes to 1 hour and try again. Error "This site cannot be reached" You likely entered a search query (e.g., the word linkedin) in the URL bar. Proxy providers block the use of search engines (Google, Bing) to save traffic. Solution: Always enter the direct address of the resource, for example: linkedin.com Proxy in GoLogin does not match the one selected in Grinfi Sometimes you may notice that the proxy country in GoLogin differs from the country selected in Grinfi. External services (like GoLogin) use their own databases to determine IP geolocation. These algorithms often identify the nearest Point of Presence (PoP) or Autonomous System (ASN) rather than the proxy's initial routing point. In some cases, geolocation data may be outdated. This is purely a visual inaccuracy that does not affect the security of your account.

Last updated on Jul 02, 2026

Frequent Questions about the Gologin Browser

GoLogin is an anti-detect browser that Grinfi uses to create a secure, isolated environment when connecting your LinkedIn accounts. Below are answers to the most common questions regarding its use. Do I need to pay for a GoLogin subscription? No, you don't. All sessions created through Grinfi (during the connection of LinkedIn to sender profiles) are already covered by our platform. - Trial period: If you see a message in the GoLogin interface stating that your trial period has expired, simply ignore it. Grinfi sessions will continue to function without restrictions. - When a subscription is needed: You only need to purchase a license if you plan to use GoLogin for your own purposes unrelated to Grinfi automation, or if you wish to use the web version only (free access to Grinfi sessions is only available via the desktop application). Can I use a different anti-detect browser? Grinfi's entire technical architecture is built specifically on GoLogin's capabilities. Other browsers have different technical implementations, making it impossible to connect them to Grinfi. Is it mandatory to install the GoLogin app? No, installing the app is not mandatory. However, using GoLogin provides an additional layer of security. By using GoLogin, you can share created sessions with other users, allowing them to gain direct access to an account. Since the login occurs via a single GoLogin session, LinkedIn will not flag changes in IP address or device, even if accessed from a different part of the world. Does every team member need to register and install GoLogin? All LinkedIn tasks can be performed through a regular browser, but running sessions via GoLogin significantly improves security and reduces the risk of account restrictions when working as a team. Depending on your team's structure, you can choose one of three scenarios: 1. Team access: Each team member registers their own GoLogin account, installs the app, and shares the session to their account within the browser. 2. Single GoLogin account: Only one GoLogin account is created, and all team members are given the login credentials to use it. 3. Administrative approach: Only one responsible person installs and manages the GoLogin browser without sharing access with other team members.

Last updated on Jul 02, 2026

Email Connection Troubleshooting

When setting up email accounts, you may encounter technical limitations from email providers or authorization errors. Below are the most common problems and their quick solutions. Outlook / Microsoft 365 Email fails to connect To connect Outlook and Microsoft 365 to third-party services, OAuth 2.0 authorization is required, as Microsoft has disabled Basic Authentication - using a standard username and password for the SMTP protocol. Unfortunately, connecting these email services to Grinfi is currently unavailable. Authorization Error When Connecting Gmail If you are connecting a Google email account and receive an authorization error, it is most often due to an incorrect password. Common mistakes include: - Using the primary password instead of an App Password: For security reasons, Google blocks login attempts via third-party services using your regular email password. To connect, you must use an App Password. The Difference: You create your primary password yourself. However, an App Password is a unique code consisting of 16 random letters generated automatically by Google. You can find a step-by-step guide on generating an App Password during the first stage of the Gmail connection process within the Grinfi interface. - Password validity: If you previously created an App Password but recently changed your primary Google account password, your app passwords may have been deactivated by Google's security system. You will need to generate a new App Password. - Temporary glitches: If the password is correct but the error persists, wait 30-60 minutes and try again. We may be deploying a platform update or performing routine maintenance at that time. Connection Errors for Other Providers (Custom SMTP) If you are connecting email from a custom provider and encounter an authorization error: - Change the connection port: The most frequent cause is using SMTP port 465. Try changing the port value to 587, even if your provider's official instructions specify 465. In most cases, this resolves connection blocking issues. - Check syntax: Carefully review your authorization details (email address, password, host addresses). Make sure there are no accidental spaces at the beginning or end of the fields. - Test the connection: Try connecting this email to any other email client via SMTP to ensure there are no hidden restrictions on your provider's side. Error on an Already Connected Email If a previously connected email suddenly stops working or displays an error, you need to reconnect it to the platform. 1. Go to the list of your connected email accounts. 2. Click the three dots icon (...) next to the specific mailbox. 3. Select Reconnect from the dropdown menu. 4. Complete the connection process again to refresh the session.

Last updated on Jul 02, 2026