> ## Documentation Index > Fetch the complete documentation index at: https://docs.getswan.com/llms.txt > Use this file to discover all available pages before exploring further. # Statuses > Plain-language decoder for every status you'll see on sequences, contacts, runs, and approvals. Swan tracks status at four levels: a sequence, a contact within it, an agent run, and an approval. This page decodes each one. For full behavior, see [Replies and stop conditions](../outreach/replies-and-stop-conditions), [Approvals](../outreach/approvals), and [Monitoring trigger runs](../triggers/monitoring-runs). ## Sequence status | Status | Meaning | | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | Awaiting approval | The sequence (or a contact's queued enrollment in it) is waiting on a human decision before anything sends. See [Approvals](../outreach/approvals). | | Enabled | The sequence is active and its contacts are moving through their steps normally. | | Stopped | The sequence has been manually paused. Active contacts are held where they are; nothing further sends until you resume. | ## Per-contact status Every contact enrolled in a sequence has its own status, independent of the sequence's state. | Status | What it means | What to do | | ----------------- | ------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | Pending | Queued, hasn't started its first step yet. | Nothing — it'll start on the next scheduling pass. | | Running | Actively moving through steps. | Nothing. | | Waiting on limits | The assigned sender has hit its daily or weekly cap. | Nothing — it resumes automatically once the sender's counter resets. See [Sending limits](../outreach/sending-limits). | | Finished | Reached the end of the sequence, or stopped in a way that counts as complete (see reasons below). | Check the reason if you're unsure why it ended. | | Stopped | Paused before finishing, for a reason that isn't a normal completion (see reasons below). | Check the reason — some resume on their own, some need action. | | Error | Hit an issue Swan can't resolve automatically. | Fix the underlying issue, then manually restart the contact. | ### Why a contact stopped or finished | Reason | What to do | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Contact replied | Nothing — a human takes it from here. See [Replies and stop conditions](../outreach/replies-and-stop-conditions). | | Already contacted manually — sender messaged this contact directly, outside the sequence | Pick up the conversation yourself, or resume the sequence if you still want Swan's steps to continue. | | Sender removed — the connected account assigned to this contact was disconnected | Reconnect the same account; the contact resumes automatically. | | Sequence deleted | Nothing — expected. | | Manually stopped — you stopped the sequence or contact by hand | Resume manually if you want it to continue. | | Awaiting approval — parked pending a human decision | Approve or reject from the app or Slack. See [Approvals](../outreach/approvals). | | Excluded — the contact or company was excluded from outreach (a legacy stop reason; current versions block enrollment up front rather than stopping an already-active contact this way, so you're unlikely to see it on new runs) | Remove the exclusion to re-include them. See [Tags, lists, and exclusions](../data/tags-lists-and-exclusions). | | Taken manually | Nothing. | | Connection rejected — the LinkedIn request was declined, and the sequence doesn't use email | Nothing — this only appears on LinkedIn-only sequences. On a sequence that also has email steps, a rejected connection request just skips the remaining LinkedIn steps and the contact keeps going on email. | | Connection expired — not accepted within the wait period (2 weeks from when the invite was sent), and the sequence doesn't use email | Nothing — same as rejected, but for a timeout instead of a decline. | | Already connected — Swan detected you're already connected on LinkedIn | Nothing — the connection request step is skipped and the sequence continues to the next step. | ### Why a contact errored A contact only lands in **Error** once every channel its sequence actually uses has stopped working for it — a single failed channel on its own doesn't error the contact, it just narrows what's left to run. See [Replies and stop conditions](../outreach/replies-and-stop-conditions) for the full per-channel failure model. | Reason | What to do | | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | | All channels failed — every channel the sequence uses (LinkedIn, email, or both) has stopped working for this contact | Fix the underlying issue on the failed channel(s) — for example, correct a LinkedIn URL or check the email address — then manually restart. | | Unexpected error — Swan hit a technical issue it couldn't recover from | Manually restart the contact; contact support if it keeps happening. | Recently invited on LinkedIn no longer errors a contact by itself — Swan tries to recover automatically first (reusing an existing invitation), and only counts as a LinkedIn channel failure if that recovery doesn't work. See [Replies and stop conditions](../outreach/replies-and-stop-conditions). ## Run (execution) status | Status | Meaning | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------- | | Pending | Queued, hasn't started yet. | | In progress | Actively running. | | Completed | Finished — including runs that only partially completed their instructions; check the run's summary for what it actually did. | | Failed | Hit an unrecoverable error. | | Cancelled | Stopped before finishing, deliberately. | | Awaiting approval | Paused on a step that needs your sign-off before Swan continues. | See [Monitoring trigger runs](../triggers/monitoring-runs) for where to find these and common failure reasons. ## Approval status Two separate things use the word "approval": | Context | Statuses | Meaning | | ------------------------------------------- | -------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | A step or sequence waiting on your decision | Awaiting approval, then approved or rejected | A queued step or sequence pauses as awaiting approval until you approve or reject it. See [Approvals](../outreach/approvals). | | A task on the Desk | Pending, Reviewed, Discarded | Pending needs attention; Reviewed means you handled it; Discarded means you dismissed it. Neither changes the underlying sequence or data. See [Desk and tasks](../workspace/desk-and-tasks). | ## Common questions **A contact shows "waiting on limits" — is something broken?** No — its sender hit a sending cap, and it resumes automatically once the counter resets. **My sequence shows "awaiting approval" but approving returns 0 contacts affected — why?** Approval acts only on contacts whose reason is currently "awaiting approval." If none have that reason anymore (already approved individually, or moved on), there's nothing left to affect. **What's the difference between "stopped" and "finished"?** "Finished" means the contact reached a natural endpoint (a reply, end of sequence, connection outcome). "Stopped" means something paused it before that (a manual stop, a disconnected sender, an approval gate). **Do I need to do anything when a contact is "errored"?** Yes — errors don't retry automatically. Since a contact only errors once every channel its sequence uses has failed, fix the underlying issue on the failed channel(s) (correct a LinkedIn URL, check the email address) and manually restart the contact. **Does discarding a Desk task stop the sequence it's about?** No — resolving or discarding a task only manages your task queue and never changes the underlying sequence or data.