Support.

This is the safety latch, and it is deliberate. When the desktop application sees a signal from LinkedIn (an invitation limit, a weekly limit, “unusual activity”, a security verification page, or a captcha challenge actually covering the screen) it stops all actions and stays stopped. The latch is written to disk, so restarting the app or your Mac does not clear it.

That is intentional: continuing to act after a restriction signal is the fastest way to turn a temporary limit into a permanent one.

What to do:

1. Open LinkedIn in your normal browser and confirm the restriction is really gone. Complete any verification LinkedIn is asking for, and make sure no limit message is showing.
2. Wait. If you hit an invitation or weekly limit, only time clears it.
3. In the ReplyMama desktop app, clear the restriction once you have confirmed the account is healthy. The app reports the exact signal it caught (for example unusual_activity or invitation_limit) so you know what it reacted to.

If the app reports corrupt_latch, it could not read its own latch file and failed safe. Clearing the restriction in the app resolves it.

The desktop app drives a browser profile on your Mac. If that session expires, or LinkedIn logs it out, every action that needs a signed-in session will fail.

What to do:

1. Open the app and check the session indicator on the Desktop screen.
2. If it is not signed in, sign in to LinkedIn in the browser window the app opens. The app detects the session and resumes on its own. You do not need to restart it.
3. LinkedIn sometimes shows a login wall even on a valid session. If signing in again does not stick, check LinkedIn in a normal browser first: a checkpoint or verification there will also block the app.

Work through these in order. Each one is a real gate in the pipeline:

1. Is the desktop app open and paired? All LinkedIn actions run locally. If your Mac is asleep or the app is closed, the queue waits.
2. Is the campaign actually running? A campaign that is paused, or that has finished its sequence, will show no new activity.
3. Have you hit your daily cap? The safety gate limits how many actions can run per day and spreads them across your sending window. Once the day’s cap is reached, the rest is scheduled for tomorrow rather than sent immediately.
4. Are you inside your sending window? Actions are only dispatched on the weekdays and hours you set in Settings.

The Analytics page shows failures separately from successes, so a run of failed actions is visible there rather than looking like silence.

Most likely they replied. A reply stops the sequence for that lead on purpose. Every queued step is cancelled so the automation does not keep messaging someone who has answered you. That is a feature, not a failure. You can see the reply in the Inbox, and the conversation is linked to the contact under Contacts.

Open the campaign and look at the failed actions, or check the Analytics page, which counts failures separately. Failures are recorded with the reason the desktop reported.

Common causes: the lead’s profile was removed or is no longer reachable, the connection request was already pending, or LinkedIn showed a restriction signal mid-run. If many actions fail at once, treat it as a restriction and see the first entry above.

AI drafting is included from Practitioner upward. Novice does not include it, which is why the drafting button is absent on that plan rather than disabled. If your plan includes it and the button reports that AI is not configured, that is a server-side configuration problem on our side. Contact us and we will fix it.