Skip to content
Speiros

Speiros 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.

Ask assistant

Get an answer based on these guides. No account required.

Understand and recover

Diagnose a blocked or failed sequence

Identify the execution condition before retrying or changing a plan.

In this collection
On this page

Use the current sequence and its evidence to identify why the next touch has not happened.

Before you begin

Know the intended candidate and Recruiting mission. Avoid creating replacement outreach while the outcome of an existing task is uncertain.

Check the current sequence

  1. Open Work → Sending plan, filter to the Mission, and inspect Problems, Waiting, or Paused as appropriate.
  2. Open the candidate’s row. Read What happens next, Planned touches, and the displayed blocker.
  3. Inspect Execution diagnostics, Proof, and Durable history. Check whether a send is provider-confirmed, still queued, or uncertain.
  4. Verify the assigned Sender’s current connection and schedule in Settings → Sender, and the Mission’s Contact channels authorization.
  5. Check the candidate’s Do not contact status and any existing conversation before planning further contact.

Resolve the correct condition

  • A reviewable draft needs sequence approval.
  • A relative follow-up can wait for a prior confirmed send; read its condition rather than inventing a date.
  • A Mission or LinkedIn hold needs the matching lifecycle control.
  • A manual global LinkedIn stop can offer Resume sending. That action does not clear automatic or scoped protections.
  • An eligible failed task can offer Retry task. Retry that task rather than launching a duplicate sequence.

If the result remains uncertain

Refresh current state and read the provider evidence again. Partial evidence or Ambiguous truth is not confirmation of either success or safe failure. Contact Support with the sequence and visible diagnostic references before another send.

Result and next step

Check the updated next action and history. A recovered task can still wait for execution gates. Follow Sending plan until the outcome is recorded.