Skip to content
Lemma

Lemma Help Center

Find the next step

Enter at least two characters

Search by the job or state you see.

Results are grouped by guide, so each article is one keyboard stop.

Channel readiness

Pause, reconnect, or replace a Sender

Stop sending, restore the same account, or move future work to a different LinkedIn identity.

In this collection
On this page

Choose the smallest action that matches what changed.

Pause or resume

Use Pause when you want the Sender to stop becoming eligible while keeping its identity and current plan visible.

Inspect current work

Open Outbox. Note any touch already in progress and any Sequence waiting on this Sender.

Pause the Sender

Open Settings → Sender and choose Pause. Confirm the execution badge becomes Paused.

Resume deliberately

After the reason for the pause is resolved, choose Resume sending and confirm the state becomes Ready. Reconnecting the account is not a substitute for resuming an intentional pause.

Reconnect the same account

Choose Reconnect when the provider session for the same LinkedIn identity expired or became unusable.

After the provider flow:

  1. verify that the LinkedIn identity did not change;
  2. check the execution state and inline reason — Reconnect preserves the existing execution status;
  3. inspect upcoming Sequences before retrying any action.

A paused Sender stays paused after reconnecting. Reconnect is not a substitute for Resume sending.

Replace the account

Choose Replace only when Lemma should use a different LinkedIn identity.

Replacement can be blocked

Lemma rejects replacement while planned or in-flight work still references the current Sender. Existing tasks are never reassigned to the new account.

If replacement is blocked:

  1. open the affected Mission and Outbox Sequences;
  2. hold, stop, complete, or let the referenced work settle as appropriate;
  3. retry Replace only after no non-terminal work references the Sender.

A successful healthy replacement normally makes the new Sender Ready after verification. Recheck the identity, schedule, daily targets, Missions, and upcoming Sequences. Approval for one Sender does not automatically describe the operational intent for a different identity.

If an external outcome is unclear

Do not reconnect, replace, or retry merely because an internal state is slow to update. Open History and provider evidence for the affected Sequence. A duplicate LinkedIn invitation or message is harder to undo than a deliberate wait.

Next action

If the Sender is healthy but work still cannot progress, follow Resolve a Sequence problem.