# Statuses

> Every state an agent, prospect, run and sequence can be in, and what moves it.

Source: https://rivomi.com/docs/reference/statuses



## Agent [#agent]

| State      | Meaning                                                                | Moves by                          |
| ---------- | ---------------------------------------------------------------------- | --------------------------------- |
| `draft`    | Created, never launched. Finds nobody, sends nothing.                  | `rivomi_set_agent_state` → `live` |
| `live`     | Searching its sources every six hours. Sending too, if outreach is on. | → `paused`                        |
| `paused`   | Search stopped, every sequence held, nothing cancelled                 | → `live` resumes where it stopped |
| `archived` | Retired in the app                                                     | Not reachable from a tool         |

## Prospect [#prospect]

The `status` filter on `rivomi_search_prospects`:

| Status       | Meaning                                                               |
| ------------ | --------------------------------------------------------------------- |
| `new`        | Found, not judged yet                                                 |
| `qualified`  | Scored as a fit, waiting to be contacted                              |
| `contacted`  | Invitation sent                                                       |
| `accepted`   | Connected                                                             |
| `replied`    | Wrote back                                                            |
| `not_fit`    | Ruled out by the targeting                                            |
| `suppressed` | Do not contact (labelled `fit: "not"`, or on the do-not-contact list) |

`enriched`, `scored`, `drafted`, `disqualified` and `screened_out` are raw pipeline states and
match exactly.

## Run [#run]

`queued` → `running` → `done` or `failed`. Poll `rivomi_get_run` on `finished`, not `status`.
One failing signal does not fail an agent's run: it is recorded against that signal and the run
carries on.

Kinds: `sweep` (an agent or workspace search), `import` (a post's engagers), `discovery`,
`score` (enrich and rate), `draft`.

## Sequence (enrollment) [#sequence-enrollment]

| State       | Meaning                                                                                       |
| ----------- | --------------------------------------------------------------------------------------------- |
| `queued`    | Assigned to a sender, waiting for its slot inside working hours and the daily cap             |
| `invited`   | Connection request sent                                                                       |
| `accepted`  | They connected; follow-up messages run on their delays                                        |
| `replied`   | They wrote back. The sequence stops and the thread is in the inbox.                           |
| `done`      | Every step sent, no reply                                                                     |
| `paused`    | Held. `rivomi_set_enrollment_state` → `active` resumes it exactly where it stopped.           |
| `withdrawn` | Stopped with the invitation withdrawn on LinkedIn. Final.                                     |
| `failed`    | Could not proceed (for example, already connected when first-degree connections are excluded) |