Job Lifecycle & Statuses

This page explains how a job moves from creation to a completed, failed, or warning run.

The normal lifecycle

Creating a job puts it in pending. The agent picks it up at its next check-in, then reports running while restic works. A completed run becomes success and records a snapshot ID. An error, stop, or timeout becomes failed. A run that creates a snapshot after processing zero files becomes warning.

Status or badge	Meaning
pending	The job has never run, or it has been flagged but the agent has not picked it up.
running	A backup is in progress and the row shows reported progress.
success	The last run completed and created a snapshot.
failed	The last run errored, was stopped, or exceeded its maximum duration.
warning	A snapshot was created but zero files were processed. Check for an empty or incorrect source path.
stalled	A running job has reported no progress for many hours. The machine may have slept or the agent may have stopped.
force-run	You flagged the job to run on the next check-in, even if the job is disabled.

Controlling a run

Run now sets a flag. The agent sees it on its next check-in, usually within about two minutes. Stop asks a running agent to terminate the backup; the agent checks for that request during a run and the result is marked failed. Mark as failed is for a run whose agent is unreachable or has not responded: the dashboard marks it failed and requests a stop if the agent later sees the request.

If a job is stalled, check the agent and its log first. Then use Stop or Mark as failed before trying Run now again.

First runs and run limits

An enabled job that has never run starts on the next agent check-in without waiting for its recurring schedule. Individual runs have a maximum duration of roughly half a day; longer runs are terminated and marked failed.

Warning

Deleting a job or agent permanently removes its run history and snapshot-ID records. The repository data remains, but Vecta can no longer identify those snapshots for you. See Restoring Data for the manual recovery path.

What's next

See Jobs for editing and scheduling, or Restoring Data to use a recorded snapshot.