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 · 13 pages · about 1 hr 10 min of reading estimated so far, across 4 of the 13 pages

  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
    • 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​

The estimates are authored per page and not every page has one yet, so a module or role total covers only the pages that do — treat it as a floor, not a full syllabus.

Related topics