Skip to main content
LinkedIn steps run in your own browser through the extension, not on a server. If one is stuck, the cause is almost always local.

Work through the checks

Go in order: the likeliest cause comes first.
1

Check the extension is installed and signed in

Open the sender’s LinkedIn tab from Senders & mailboxes. If it shows a connection token instead of a connected account, install the extension and paste the token into its side panel.
2

Read why the next step waits

When the time between steps, a limit or the sending window holds the next step, the tab’s queue line says so and until when. The side panel shows the same line, such as “Next step in 6 hours · Daily limit reached”.
3

Check the sending window

A sequence’s LinkedIn steps run only inside its sending hours, in the sender’s timezone. Outside them the queue line reads “Outside sending window”, and the step runs once the window opens.
4

Check your browser is open

Steps queue until a browser with the extension is open. The tab reads Active, Idle or Not seen beside each browser.
5

Check the step is approved

On Manual run, every step waits for Approve in Tasks, and the sender’s queue counts it only once approved. Checks of your own inbox, sent requests and new connections run without it.
6

Check the sequence is running

A paused sequence holds all its LinkedIn steps, approved or not, and Detail in Tasks reads “Sequence paused”. Open the sequence and click Resume sequence to put them back in line.
7

Check the LinkedIn account is still connected

A disconnected account stops every queued step. Reconnect it from the sender’s LinkedIn tab.
8

Check for a verification checkpoint

LinkedIn sometimes asks to verify the account, which holds the queue and opens a verification page in your browser. Complete it there and the queue carries on.
9

Check the limits

Limits caps each action per day, and per week where a weekly limit is set. Once a ceiling is reached, its steps wait until a midnight in the sender’s timezone frees a slot.

Good to know

No. It works through the session your browser already holds, and disconnecting it never touches your LinkedIn account.
The hours run on the sender’s timezone, which may not be yours. Check Timezone on the sender’s Settings tab, or pick one zone under Timezone in the sequence’s Schedule. See Schedule and sending window.
No. Checks of your own inbox, sent requests and new connections run at any hour, and so does a step from Try a step.
Each sender runs one step at a time, and waits at least its Time between steps between two, plus a little more at random. Set it under Limits on the sender’s LinkedIn tab, from 1 to 60 minutes.Checks of your own inbox, sent requests and new connections wait only a minute or two after a step, and never hold up the next one.
Oneprofile hasn’t seen the acceptance yet. It checks the sender’s newest connections in the sender’s own browser, so keep a browser with the extension open for that sender, and keep the extension up to date.A busy account can see an acceptance late. If the wait runs out first, one look at the person’s profile settles it, and that look waits for Approve in Tasks whenever the sequence’s LinkedIn steps do. See LinkedIn steps.
The run mode beside Limits on the sender’s LinkedIn tab decides whether queued steps run on their own. On Automatic run they run within the limits, and on Manual run each waits for Approve. Start on Manual run until you trust the sequence.
The step failed in the browser, for example because Oneprofile could not find LinkedIn’s Connect button. The contact stops at that step, and hovering Interrupted on the sequence’s Audience tab shows the reason. Nothing retries a failure on its own.A step whose browser went offline mid-step is not a failure. The contact waits under Browser offline, and the step finishes once the browser is back. A message or InMail that may already have gone out still waits for Retry.A step cut off mid-run, by a restart or a page that would not load, runs again in place first. So does a step where LinkedIn never answered a button, such as a laptop going to sleep right after Connect: it checks the profile again before it presses anything. It stops this way only after four such tries. A tab you closed and a lost connection never count toward the four.Open the step under Failed in Tasks and click Retry. You can also choose Retry in the contact’s row menu, or Retry all on the banner above the list. See LinkedIn steps for what a retry sends.A withdraw that found the person already connected stops them too. Their row reads Already connected and has no Retry, since there was nothing to withdraw.

Next steps

Connect LinkedIn

Install the extension and connect a sender’s account.

LinkedIn steps

Every LinkedIn action, its conditions, and its limits.