LinkedIn account cards: status, Reconnect, Pause and Remove

How to do it

1. Read the stats strip at the top: Accounts (how many are connected, how many are Active, and how many need attention — a reconnect, or a code to enter — or are signing in or paused); Invites Today, Messages Today and Profile Views Today (what Active accounts used today out of their combined daily limits, with a bar); and Acceptance · 7 Days (of the invites sent in the last 7 days, the share of people now connected — "N of M invites").
2. Each account has a card: its photo (or initials) with a status dot, the name and status pill, its LinkedIn headline (the login email when there isn't one), and "Session in <country>", plus "· residential IP" when it has one assigned.
3. The status pill: Active (runs LinkedIn steps); Paused (you paused it, or it lost its sender seat); Connecting… (a sign-in is running — View Progress follows it); Approve the sign-in or Waiting for a code (LinkedIn wants a code or an approval in its app — press Continue on the card); Sign-in failed or Reconnect needed (LinkedIn turned down the sign-in or no longer accepts the session — the card gets a red border and a banner with the reason and a Reconnect button).
4. The three tiles show today's use of each daily limit — Invites, Messages, Views, as used / limit with a bar. The row below covers the last 7 days: Invites · 7d (connection requests it sent), Accepted (how many of those people are now connected, with the rate), Replies (people who replied to it on LinkedIn) and Campaigns (campaigns using it that haven't finished).
5. The footer's session line says when MailFleet last confirmed the account was signed in to LinkedIn — "Session OK · 4 min ago". A signed-out account reads "Signed out · last OK <date>"; "Not checked yet" means no check has passed so far.
6. To reconnect, press Reconnect in the banner (or ⋯ → Reconnect). For a password account MailFleet signs in again with the saved details and shows the same code / app-approval steps as a first connect; if LinkedIn turns the password down (it was changed), press Enter New Password and type the new one. For a cookie-connected account it asks you to paste a fresh li_at cookie. Reconnecting keeps the account, its campaigns and its history — sent invites and messages stay in your reports.
7. To stop an account for a while, press Pause in its footer: nothing more goes out from it, including steps already queued on it — those are taken back within a minute and go out from another of the campaign's Active accounts, or wait until you resume it. Resume brings it back (resuming an account with no saved session signs it in again, shown in the connect dialog). Pause is greyed out on an account that needs reconnecting or is still signing in.
8. ⋯ → Refresh Session re-reads the profile's real name and photo from LinkedIn with the saved session. It opens a real browser and takes up to a minute (the footer reads "Refreshing…"), and runs at most once every 10 minutes per account — until then the item is greyed out and says when it can run again.
9. ⋯ → View Campaigns opens your LinkedIn campaigns.
10. ⋯ → Remove Account asks first and lists what happens: its queued LinkedIn steps are cancelled and those leads go back to their campaigns, to continue from another LinkedIn account the campaign uses where they can — or wait until you pick one in Edit → Senders; it comes off the campaigns using it; its sent invites and messages are deleted from MailFleet, so they no longer count in campaign reports (replies stay); nothing changes on LinkedIn — invites already sent stay pending there. Its sender seat is freed. This can't be undone.

Good to know

• Every Active account gets a lightweight "still signed in?" check every 15 minutes, independent of campaigns. An account is only flipped to Reconnect needed after two consecutive failed checks, so a single network blip never disconnects it; a real browser or proxy fault is not counted against the session at all.
• When an account is confirmed down you get a critical notification, "LinkedIn account <name> needs reconnecting", listing how many queued actions are waiting and which campaigns are on hold. It is sent once per outage, not once a day.
• While an account is down, leads whose LinkedIn action failed because of it are not penalised: they wait and are retried every hour once the account is back.
• A campaign never skips a LinkedIn step for want of an account. If none of its chosen accounts can take the step (all paused, needing reconnect or out of today's allowance), the lead waits at that step and is retried every hour; the lead's activity reads "Waiting for a connected LinkedIn account — LinkedIn step retries hourly".
• A paused account sends nothing — not even a step that was already queued and due. Its queued steps are cancelled and their leads go back to their campaigns: a profile view or an invite goes from another Active account the campaign uses, or waits as above; a message only ever goes from the account the lead is connected with, so it waits for you to resume that account.
• If your sender seats drop below the number of connected accounts (a seat subscription lapsed, or a move to a plan with fewer seats), the newest accounts beyond the allowance are paused automatically and their cards say "Paused — no sender seat for this account. Add a seat or disconnect another account, then resume."; Resume is refused until you add a seat or remove another account.
• An account whose LinkedIn note allowance is spent for the month shows "Invites go out without a note — this month's note allowance is spent." on its card; invites keep going out without the note (see LinkedIn daily limits).
• Active accounts are queued to read their LinkedIn inbox every 20 minutes and, while invitations are outstanding, to scan their connections list every 2 hours.