Skip to main content

Operator learning path

This is the order to work through the Operator pages. It starts with reading a normal day, then moves to responding when something fails, and finishes with the tools for tracing an incident after the fact.

You don't have to follow it end to end. Each module stands on its own, so it also works as a checklist for one area you're picking up.

How to read a module

Each module runs from the task to the detail: the how-to page first, then the concept behind it, then the full reference, and finally an end-to-end scenario where one exists. Stopping after the how-to page is a perfectly good outcome if that's all you need today.

5 modules · 14 pages · about 4 hr 11 min of reading

  1. Daily run basics

    What you'll be able to do
    • Explain how a workflow goes from built to complete and why a job may be waiting
    • Recognize pending-term as a transitional, not stuck, state
    • Navigate the Processes page (Job View / Workflow View), read a run, and apply single and bulk actions
    • Schedule a workflow into the run for one date or a range of up to 31 days
    • Act on one job or workflow instance, or on several at once with Bulk actions
    • Add a job defined on the workflow to a workflow instance that is already running
    • Correct a job on a running instance, and promote the edit with Push Changes to Workflow
    • Interpret any job or workflow status and know which actions it accepts
  2. Responding to failures

  3. Event log

    What you'll be able to do
    • Read an event's fields and use status, source, and correlation to trace what happened
  4. Vision

  5. Transitioning from OpCon Classic

Where the time estimates come from​

Each page's time is its estimated read time, worked out from the page's word count at about 200 words a minute. It is the same time the page shows under its title, and each role's total adds up the pages in its path. It measures reading, not doing: allow extra time for any steps you carry out in Continuum as you go. Reference pages run long because they cover every setting, so you will often look up the part you need rather than read one end to end.

Related topics