In most cases, message delivery issues in grinfi can be identified and resolved manually. In this article, we’ll walk you through the most typical problems:
Automation is paused or out of schedule
- Make sure the automation is enabled. You can check this in the Automations section - the toggle should be blue.
- Check whether the automation schedule allows it to run at the current time. To do this, go to Automations => select the desired automation => click "..." => Config. In the pop-up window, you'll see the schedule it follows.
Another possible cause - a mismatch between the automation schedule and the sender profile schedule -is discussed in this article.
Message sending tasks in Auto Tasks keep rescheduling but are not being executed
If a task shows it’s about to run, but at the scheduled time it just moves to a later time instead of being executed, this might indicate a lost connection with the server/proxy, or that the platform is currently being updated.
Platform updates typically take up to 30-40 minutes, after which all tasks will resume automatically.
Reconnecting to the server can take a few hours, but you can manually try switching your profile to another active server:
Go to Sender Profiles, click Manage => Stop, wait 5 minutes, then click Run (located below the sender profile name, next to the status).
This will trigger a reconnection attempt to a different working server.
Manually typed message is not sending in the grinfi messenger
If you try sending a manual message via the messenger and it stays stuck in a loading state (similar to what’s shown in the marked area on the screenshot), this could mean:
The connection with the server is lost. As mentioned earlier, this will usually restore automatically within a few hours. You can also manually attempt to switch to a different server.
Sender profile is outside its working hours. The message will be sent as soon as the active hours begin.
Sender profile status is "Log out"
Messages may not be sent because the sender profile got disconnected from the platform. You can check this in the Sender Profiles section - if the status says "LinkedIn is logged out", you'll need to reconnect the profile.
You can find instructions on how to do this here тут.
Contacts are paused
If you see that in an automation, some contacts have the status "in progress" during the message sending step, but they’re not moving forward and receiving messages for a long time, those contacts are likely in the "paused after reply" status.
This means the contacts previously replied to a message from another automation, and the platform automatically paused communication with them.
This feature helps prevent unwanted or spammy messages. Once a contact replies, all current and future automations with messaging steps are paused for that person until you manually allow communication to resume.
*steps like time delay, like the latest post, and triggers will continue to run regardless of contact status. However, once the contact reaches a message sending node, the automation will pause and wait for your permission.
To remove the "paused after reply" status, you need to go to the Manual Tasks Section => Automation. Use the filter to select the specific automation you’re working with. Then you’ll see a list of contacts who are currently paused in that automation.
You can either unpause a single contact - click on the contact => then click Automation paused after reply => Unpause automations.
Or unpause multiple contacts at once - select them and click Run in bulk.
