Task State is the explicit lifecycle status of a unit of work in RankGear — for example queued, running, succeeded, failed, interrupted, or complete. It tells you exactly where a job is right now, without you having to guess.
| Term | Task State |
|---|---|
| Category | Product and Workflow |
| Also known as | Job State, Row State |
| Where it appears | Bulk Runs and active-work indicators |
What it means in RankGear
Every job RankGear runs — a single analysis, or one row inside a larger Bulk Run — carries a state that reflects its position in the work lifecycle. You see it most clearly in Bulk Runs, where each row reports its own status as the batch moves along, and in the active-work indicators that show what RankGear is currently doing. The state is not a score or a quality judgment; it is a plain record of whether a task is waiting to start, in progress, finished cleanly, or stopped because something went wrong.
How to interpret it
Read Task State as one part of a three-part check: the inputs you selected, the current state of the task, and the artifact RankGear says it produced. A succeeded or complete state means the job finished and a result should exist — open the report or output to confirm it. Running and queued mean the work is still underway, so waiting is the right move rather than re-running. Failed and interrupted are the states that ask for action: a failed task hit an error and produced no usable result, while an interrupted task was stopped partway (a cancelled run, a closed session, a lost connection) and may need to be resumed. When rows in a Bulk Run disagree, the state on each row — not the batch as a whole — is the reliable guide to what actually completed.
| State | What it tells you |
|---|---|
| Queued | Accepted and waiting its turn; no work has started yet. |
| Running | In progress now; let it finish before acting. |
| Succeeded / Complete | Finished cleanly; a result or report should be available to open. |
| Failed | Stopped on an error; no usable output was produced. |
| Interrupted | Stopped partway; may be resumable rather than restarted from scratch. |
Example
You start a Bulk Run over forty target pages before stepping away. Coming back, the run list shows thirty-two rows at succeeded, five still running, two failed, and one interrupted after a dropped connection. Rather than re-running the whole batch, you open the reports for the thirty-two that succeeded, wait on the five in progress, look at the error on the two failures, and resume the single interrupted row — the state on each row tells you precisely which of those four responses each one needs.
Important considerations
- Task State describes RankGear’s own workflow and navigation — where a job sits in its lifecycle — not a ranking signal or a search-engine score by itself.
- A succeeded state confirms the job finished, not that the finding is favorable; always open the actual artifact to read the result.
- In a Bulk Run, trust the per-row state over any single summary label, since rows can finish, fail, or be interrupted independently.
- An interrupted task is often resumable, so check before restarting from the beginning to avoid repeating work that already completed.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.