# Job History

The **Operations > Scheduling** section includes a **Job History** for both the
[manual scheduler](../manual-scheduler) and the
[policy scheduler](../policy-scheduler) that lists all jobs that have run,
whether they succeeded or failed, along with any jobs that are currently
running.

![](../images/manual-scheduler-history.png)
![](../images/policy-scheduler-history.png)

## Job details

Each job has a details popup with the following information:

- **Job ID** - a unique identifier for the job
- **Status** - the current state of the job: `succeeded`, `failed`, or `running`
- **Restore Point** - the restore point produced by the job, available once the
  backup job completes
- **Progress** - the restore point ID, number of objects processed and bytes
  stored so far
- **Resources** - a graph of CPU and memory usage over the job's runtime, hover
  over a point to see the exact values at that moment
- **Network** - a graph of network throughput over the job's runtime
- **Recent Paths** - a live list of the last files being processed, each showing
  whether it has `succeeded`, `failed`, or is still in `progress`
- **Output** - the full log output for the job, useful for diagnosing failures

{{< figure src="../images/job-info-1.png" class="max-w-150 mx-auto" >}}
{{< figure src="../images/job-info-2.png" class="max-w-150 mx-auto" >}}

If a job is currently running, the output and recent paths update in real time.
A **Cancel job** button is available to stop the job.

Failed or successful jobs from the manual scheduler can be retried directly from
the job history list. This is not available for jobs triggered by the policy
scheduler, as those are fully managed by the policies engine.

{{< figure src="../images/job-info-3.png" class="max-w-150 mx-auto" >}}

## Jobs and Schedules on Apps

Each app ([sources](../../apps/sources), [stores](../../apps/stores) &
[destinations](../../apps/destinations)) also surfaces scheduling information on
its own details page:

- The **Dashboard** tab lists all past and upcoming jobs involving that app,
  scoped to that app only.
- The **Scheduling** tab lists all schedules that involve that app, so you can
  see at a glance what is configured to run and when.

![](../images/connector-jobs-1.png) ![](../images/connector-jobs-2.png)