How workflows work
- Synopsis
- Full Details
In briefA workflow is a scheduled, dependency-ordered set of jobs. Frequencies, calendars and build settings decide when its jobs are eligible; job, threshold, resource and expression dependencies decide their order; agent assignment decides where each runs; and events fire commands in response to outcomes. Workflows are versioned and deployed to environments.
WhereDesign › Workflows, where a workflow is built in the workflow editor. Its run is watched on Operations › Processes — see How the daily run works.
When
- You are designing a workflow and need the model behind it.
- A job did not run when, where or in the order you expected.
- You are deciding between a specific agent and an agent pool for a job.
How
- Add jobs, each with a job type and an agent assignment.
- Give each job a frequency, with its build status and timing settings.
- Add the dependencies that order the jobs, and any events.
- Commit a version and deploy it to an environment.
- A job dependency can wait for success, failure or any result.
- Build Status values On Hold, Do Not Schedule, To Be Skipped and Disabled are by design; check them before treating a missing job as a fault.
- Allow Multi-Instance builds a workflow as several named schedule instances for the same date.
- Exceeded Max Runtime fires while the job is still running; the job's status does not change.
A workflow in OpCon Continuum is a scheduled, dependency-ordered set of jobs. It defines what runs (the jobs), when it's eligible to run (frequencies, calendars, build settings), in what order (dependencies), and what should happen in response to outcomes (events). Each job runs a job type — the connectors documented separately — on an agent.
In the configuration and runtime model a workflow is represented as a schedule. Treat "workflow" (the UI term) and "schedule" (the underlying term) as the same thing.
What a workflow contains
| Part | What it is |
|---|---|
| Jobs | The units of work. Each runs a job type on an agent and has its own timing, dependencies, and events. |
| Frequencies | Rules for which days/times a job (and the workflow) is eligible to run. |
| Dependencies | Conditions that must be met before a job runs. |
| Events | Actions (commands) fired in response to job outcomes. |
| Build settings | How and when the workflow is built into a day's run. |
| Calendars / working days | Holiday calendars and working days that shape eligibility. |
- Jobs
- Dependencies
- Frequencies and Build
- Agent Assignment
- Events
- Run Lifecycle
- Versions and Deployments
Jobs
A job is configured with:
- A job definition — the job type to run (e.g. Run Command, SQL Script) plus its parameters.
- An agent assignment (how the job is placed on an agent — see the Agent Assignment tab).
- One or more frequencies with runtime settings (timing, retries, reruns).
- Dependencies (what must be true before it runs).
- Events (what to do on certain outcomes).
- Properties, tags, custom fields, and flags like disabled and multi-instance.
A workflow itself can also carry named schedule instances — see Schedule instances — so one definition builds once per branch, region, or entity for the same date rather than once per date.
Dependencies
How jobs are ordered: dependencies
A job runs only when all its dependencies are satisfied. There are four types:
| Dependency | Satisfied when |
|---|---|
| Job | A predecessor job reaches the required result — success, failure, or any — optionally on a day offset and a specific frequency. |
| Threshold | A named threshold reaches a value. |
| Resource | Enough of a named resource is available (the job reserves it). |
| Expression | A custom expression renders True. It is re-asked while the job waits; one that can't be evaluated puts the job on hold rather than leaving it waiting silently. See Expression dependencies. |
Job dependencies are how the run is sequenced; threshold and resource dependencies coordinate shared state and capacity across jobs.
Frequencies and Build
When jobs run: frequencies and build
Frequencies define eligibility. Each job's frequency carries runtime settings, including:
- Build Status — Released, On Hold, Do Not Schedule, To Be Skipped, or Disabled.
- Start-time offsets and late-to-start / latest-start / late-to-finish offsets.
- Max run time and estimated run time.
- Failure retries (whether to retry, how many times, minutes between attempts).
- Success reruns (None, Recurring Instances, or Restart Offset).
Build turns the definition into a day's run. Build settings include how many days in advance to build, how many days to build, whether to build on hold, and whether to overwrite on build. Holiday calendars and working days remove non-eligible days.
Agent Assignment
Where jobs run: agent assignment
| Mode | Behavior |
|---|---|
| Specific Agent | Runs on the chosen agent. Secondary, tertiary and quaternary agents can be set as backups: when the chosen agent cannot take the job, it runs on the first of them that can — see Backup agents. A Universal Agent job goes on its pool's queue, so any agent in that pool can run it. |
| Pool - Least Tasked | Runs once, on whichever agent in the pool asks for work first. |
| Pool - Run on All | The same as Pool - Least Tasked for a Universal Agent pool: the job runs once. A legacy agent group set to run on all fans out to one job instance per member — see Agents and agent pools. |
SMAFT File Transfer and OpCon RPA Task jobs take Specific Agent only, with no backup agents — see Which assignments a job type allows.
Events
Responding to outcomes: events
Events fire a command in response to a job outcome. Triggers:
- Job Status — a status such as Finished OK, Failed, Late to Start, Late to Finish or Skipped. See Job and workflow statuses for the authoritative set. The same list offers Exceeded Max Runtime, which is a derived condition rather than a status: it fires while the job is still running, and the job's status does not change.
- Exit Description — a comparison against the job's termination description, using Equal To, Not Equal To, Greater Than, Greater Than or Equal To, Less Than, Less Than or Equal To, Contains or Range. The comparison is numeric only when every value involved is a whole number; otherwise it compares as text. See Workflow events.
- Completion Expression — a custom expression, evaluated once when the job finishes; the command
runs only when it is
True. See Completion expression events. - LSAM Feedback — a value a legacy LSAM job's agent reports while the job runs, such as a Job Status Description, matching a pattern. Offered only for a legacy LSAM job, and not for an SMAFT file transfer; see LSAM Feedback events.
Workflows can also carry schedule-level events.
Run Lifecycle
The run lifecycle (link to runtime)
A workflow is built into a day's run, then jobs run as their dependencies are satisfied, moving through statuses to completion. Operators monitor and act on that run in the Processes view. See the runtime/Processes docs for status meanings and operator actions.
Versions and Deployments
Workflows are versioned — each time you commit your changes with the editor's save action (Commit changes to a version), a new version is created, and an earlier version can be viewed, or pinned in a deployment so an environment runs it. A version is deployed to an environment to run there; deployments are tracked, so the same workflow can move from test to production deliberately.
- Build on hold is intentional — a workflow built on hold won't run until released; it's not stuck.
- Disabled jobs and Do Not Schedule/To Be Skipped build statuses are by design — check the job's frequency settings before treating a "missing" job as a fault.
- Multiple instances means two different things, and both produce more than one row. A job
can fan out into several job instances within one run (named with a dot,
EXTRACT.US). A workflow with Allow Multi-Instance on builds as several named schedule instances for the same date (named with an underscore,PAYROLL_BRANCH1), each carrying its own property values. - A job dependency on
failureoranyis valid design — a downstream job can be meant to run when its predecessor fails.
Related topics
- How connectors work
- How the daily run works (runtime monitoring)