<!-- From https://knowledge.continuous.com/operator/get-familiar-checklist -- check that page for the current version. -->

# Get familiar as an Operator

Reading about OpCon Continuum only gets you so far. The fastest way to learn it is to do the core
Operator tasks in a test environment. Work through this checklist from top to bottom, checking
off each item as you complete it. Each item links to the page that explains it in detail.

Goal: watch the daily run and respond correctly when something needs attention.

## Monitor the run

- [ ] Go to **Operations** › **Processes** and select the environment you're monitoring.
- [ ] Switch between **Workflow View** (the workflow instances, each with its diagram) and **Job
  View** (every job, one row each).
- [ ] Open a job's detail to see its output, run summary, configuration, and status history.
- [ ] See [Monitor the daily run](https://knowledge.continuous.com/operator/monitor-the-daily-run).

## Read statuses

- [ ] Learn the status groups (On Hold, Waiting, Running, Processing Events, Finished OK, Fixed,
  Skipped, Failed, Cancelled, Under Review and Lost in Failover) and what a waiting job is waiting on.
- [ ] Recognize that a status ending **; Processing Events** is transitional, not stuck.
- [ ] See [Job statuses and actions](https://knowledge.continuous.com/operator/job-statuses-and-actions).

## Respond

- [ ] On a failed job, review the cause, then choose **Restart**, **Mark Fixed**, **Under
  Review**, or **Cancel**.
- [ ] On a waiting or held job, try **Force Start**, **Skip**, **Hold**, or **Release**.
- [ ] See [Respond to a failed job](https://knowledge.continuous.com/operator/respond-to-a-failed-job).

## Trace and triage

- [ ] In the event log, open an event and select its **Correlation ID** to trace an incident
  through every event that shares it.
- [ ] Triage a failed connector job from its output and route it to the Builder or
  Administrator.
- [ ] See [Use the event log](https://knowledge.continuous.com/operator/use-the-event-log) and
  [Respond to a failed connector job](https://knowledge.continuous.com/operator/connector-troubleshooting).

## You're ready when

You can read the run at a glance, interpret any status, take the right action on a failed or
waiting job, and trace an incident through the event log.

**Related topics**

- [Getting started with OpCon Continuum](https://knowledge.continuous.com/getting-started)
- [Glossary](https://knowledge.continuous.com/glossary)
