Add jobs to a workflow
- Synopsis
- Full Details
In briefA job starts as a Null Job when you add it with First Job or New Job (Null). On its Job Definition tab you choose the job type it runs and set where it runs; on its Frequencies tab you add the frequencies it runs on and set, for each one, when it may start, when it is late, how long it may run, and whether it retries or reruns.
- Every offset is a duration from the workflow's Start Time, not a clock time, and can reach a
later day.
00:00means not configured. - Maximum Attempts counts retries, not runs:
3allows four runs. - Backup agents are used in order, and only when the primary cannot take the job; every run tries the primary first.
- A job without a job type, an agent assignment or a required parameter blocks committing a version of the whole workflow.
- Max Run Time reports an overrun but never stops the job. Add an Exceeded Max Runtime event
with
$JOB:KILLto stop it. - Once the Latest Start Offset passes, no further retry or rerun is started.
A workflow in OpCon Continuum is a set of jobs that run in a defined order, on a schedule. You build one by adding jobs, telling each what to do, where to run, when it's eligible, and what it depends on. This page covers adding a job to a workflow and setting when it runs. Create the workflow first, in its Workflow Settings panel. The related pages cover ordering and responding to outcomes.
Business processes are made of many steps that must run in the right order, at the right time, and only when their inputs are ready. Done by hand or with scattered scripts, the order drifts, steps get missed, and no one can see the whole process in one place.
- Add a Job
- Job Timing
- Offsets
- Deadlines
- Retries and Reruns
- Next Steps
Add a Job
Add a job to a workflow
To add a job to a workflow, complete the following steps:
- Go to Workflows and open the workflow you want to edit.
- Add a job: on an empty workflow select First Job, otherwise select New Job (Null) in the tool panel on the left of the editor. Either way the job starts as a Null Job — a job that runs nothing — so step 4 is where you give it real work.
- Enter a name for the job.
- On the Job Definition tab, choose the job type the job should run from the Job Type list, then set its parameters. See the Job type catalog for each job type. To start from the job type instead, use the arrow beside New Job (Null) in step 2 and pick it from Quick Add by Job Type.
- Set the job's Agent Assignment: Specific Agent, Pool - Least Tasked, or Pool - Run on All. For a specific agent, turn on Configure backup agents to name a Secondary Agent, Tertiary Agent and Quaternary Agent: the job runs on the first of them that can take it when the primary cannot. See Backup agents. A SMAFT File Transfer or OpCon RPA Task job offers Specific Agent only, with no backup agents — see Which assignments a job type allows.
- Select Save. The job is added to the workflow and the editor closes.
Repeat for each job the workflow needs.
Finish each job before you version the workflow. A job left without a job type, an agent assignment, or a required parameter is outlined with a yellow warning border on the canvas (hover the job to see the problem) and blocks committing a version of the whole workflow — see If the commit action is greyed out.
Job Timing
Set when a job runs
To set a job's schedule, complete the following steps:
- In the job editor, open the Frequencies tab.
- Add the frequency (or frequencies) the job should run on. With more than one, use each frequency's up and down arrows to put them in the order they should be checked: the first that matches a date decides it, so a Do Not Schedule frequency goes above the one it overrides. If the arrows are disabled under a note that the workflow has its own frequencies, the workflow's list sets the order instead. See When more than one of a job's frequencies matches.
- Under Offset Information, set the job's timing for that frequency: the Start Offset, and the Late to Start Offset and Late to Finish Offset — each measured from the run's scheduled start. See the Deadlines tab: both are acted on now, where earlier builds saved them and did nothing with them. The line under Offset Information names the time zone these times are in — the scheduler's, such as Times use America/Chicago (scheduler time).
- Under Latest Offset, set the Latest Start Offset — the point past which the job should no
longer start at all. Leave it at
00:00to have no deadline; that value means not configured rather than midnight. - Under Run Time, set the Max Run Time (in min) and Estimated Run Time (in min).
- Optionally turn on Enable failure retries (Maximum Attempts, 1–999, and Minutes Between
Attempts, 0–1440) under Failure Retries, and choose a Success Rerun Mode under Success
Reruns. With Restart Offset, leave Latest Runtime Offset at
00:00for no time limit: the job reruns until it reaches Maximum Runs. Or clear Maximum Runs and set a Latest Runtime Offset: the job needs at least one of the two, and the editor says Set Maximum Runs or a Latest Runtime Offset. until it has one. - Select Save.
How each of these values is measured, and what changed in how they behave, is on the Offsets, Deadlines and Retries and Reruns tabs.
Offsets
How the offsets count
Every offset here is a duration from the workflow's start time on the job's schedule date, not a
clock time. In a workflow that starts at 08:00, a Start Offset of 06:00 makes the job eligible at
14:00.
Because it is a duration, the hours field is not capped at 23 — it goes up to 99, a little over
four days out — so a job that must start by 02:00 the morning after an 08:00 schedule takes 18:00.
Earlier builds capped it at 23:59 and a cross-day deadline simply couldn't be written.
Each group has its own Format control (Absolute or Relative). The one under Offset Information covers the start offset and both thresholds that hang off it; Latest Offset has its own. Absolute measures from the schedule's planned start, as described above. Relative measures from its actual start, so a workflow that was due at 08:00 and began at 08:40 moves that job's offset out by those 40 minutes — use it for a deadline that should follow a late run rather than hold it to the clock. A relative offset is not acted on until the workflow starts, and is re-anchored on the real start time once it does — and again every time the workflow gets a new actual start, which includes releasing or starting a run that was held part-way through. See The two Format controls and Offsets past midnight.
Earlier builds resolved these from midnight of the schedule date, so the 08:00 workflow above started its job at 06:00 — eight hours early, with nothing logged. If you set a deadline before this change and saw it firing too early, the definition needs no repair; rebuild the schedule date.
Setting one of the four back to 00:00 on an already-built job instance removes the deadline it
set from that run. A job with a time window dependency is the exception: clearing its Start
Offset, or a Latest Start Offset whose window has an end, is refused, and rebuilding the date
clears it. See
00:00 means not configured.
Deadlines
Max Run Time and the late offsets
A job set to overrun its Max Run Time used to do so silently and finish reported as a plain success. Two things were wrong and both are fixed, so check any job you set a limit on:
- The limit never reached the built job. The frequency's Max Run Time was saved and carried through deployment, and every job the build produced carried no limit at all — the only way to get one onto a run was to edit the job instance by hand. The frequency's value now reaches every built job.
- Nothing compared the elapsed time against it. The job now carries an Exceeded Max Run Time badge in the run, raises the Job Exceeded Max Runtime notification trigger, and fires any job event on the Exceeded Max Runtime trigger.
Set the value in minutes; 0 means no limit. The platform reports the overrun and does not
stop the job — to have it killed, add an Exceeded Max Runtime event with a $JOB:KILL command
(see Run events on job outcomes).
See Exceeding Max Run Time.
Late to Start Offset and Late to Finish Offset had the same problem Max Run Time did: the values were authored, saved and carried onto the job, and nothing ever compared a run against them. No job ever reached Late to Start or Late to Finish, so the Job Late to Start and Job Late to Finish notifications and the matching job events could never fire. All of that works now.
Two things are worth knowing as you set them:
- Both are measured from the run's scheduled start — the planned schedule start plus the Start Offset — and Late to Finish is measured from that start too, not from when the job actually began. A recurring run or a failure retry re-measures from its own scheduled time, so each run is checked against its own deadline.
- A job still waiting on a dependency, threshold, resource, expression or machine gets a Late to Start badge rather than the status, because the status would start the job ahead of what it is waiting for. The reporting is the same either way, and it happens once per run.
Late to Start is advisory: the job can still start, and holding the workflow does not suspend it. See Late deadlines.
Retries and Reruns
Failure retries and success reruns
A job set to retry after failing made no second attempt in earlier builds — the plan was saved and the failing job never acted on it — so a retry configuration you set up in the past and assumed was inert is live now. Two things to get right before you rely on it:
- Maximum Attempts is a count of retries, not of runs.
3allows four runs: the first, and three more. - Leave room inside the Latest Start Offset. A retry that would fall after the deadline is not
taken — the job fails at that point instead. With
3attempts30minutes apart, the deadline needs at least an hour and a half of headroom past the job's own run time.
Between attempts the job waits in Waiting: Start Time (Wait Start Time on Processes), holding the last attempt's exit code, and releases no dependents until it is genuinely out of budget — so a failure-triggered recovery job does not fire on an attempt that is about to be retried. See Failure retries.
A job set to rerun after finishing OK never actually restarted in earlier builds — the setting was saved and the running job never saw it. It works now, so a rerun configuration you set up in the past and assumed was inert is live. If a job reruns on configured instance times and a run can outlast the next one, set Instance Overlap Action: On Completion (the default) fires the elapsed time immediately, Skip waits for the next time still in the future. See Success reruns.
A job with both a run window and success reruns used to honour the window on its first run and then
restart on its interval regardless of it. It no longer does: once the Latest Start passes, no further
restart is scheduled, and a job already waiting for one ends as Missed Start Time — which retires
the rest of its cycle. Set the Latest Start to a point that leaves room for every run you expect, or
leave it at 00:00 for no deadline. See Recurring jobs and the latest-start
deadline.
The Start Offset is the other way round — it gates the first start only, because scheduling a restart supersedes it.
Next Steps
Next: shape the workflow
Once your jobs exist, use the other tabs in the job editor and the related pages to finish the design:
- Order the work: set what each job waits for. See Order jobs with dependencies.
- Schedule it: set the workflow's working days, holidays, start time and build settings. See Workflow Settings.
- Respond to outcomes: fire actions on job statuses. See Run events on job outcomes.
- Release it: version and deploy to an environment. See Version and deploy a workflow.
- A job runs a job type: the same connectors documented for each kind of work (commands, scripts, SQL, file waits, and more).
- Jobs can run on a specific agent or across an agent pool. On a Universal Agent pool, both pool options run the job once, on whichever agent in the pool asks for work first.
- Turn a job's Disabled switch on to keep it in the design without building it into any run — scheduled, automatic or as a container's sub-workflow. A disabled job is skipped before its frequencies are even looked at, its dependents treat it as absent for the date, and a workflow whose every job is disabled doesn't build at all. An Operator can still add it to a run by hand.
- Need the diagram outside the editor — for a change record or a review? SVG Image in the Canvas Tools panel downloads the whole graph as a file. See Export the canvas as an SVG image.
- A crowded canvas is a filter away from a readable one. The panel down the left of the editor finds a job, hides whole categories of card, and moves the view around — including a minimap and a Re-layout control for when cards end up overlapping. See The workflow editor tool panel.
- Check what would build before you commit. The Forecast switch redraws the canvas as the build for a date you pick, using your unsaved edits — so you can see which jobs would run, and when, before versioning anything. See Forecast view.
- Running SAP R/3 jobs? Check SAP Job Numbers, among the workflow toolbar's actions, compares the SAP job number stored in every SAP R/3 Job across your workflows with the SAP system, and saves the numbers you choose to correct. See Checking every stored SAP job number.
Related topics
- Job configuration — full configuration reference and troubleshooting
- Export the canvas as an SVG image — getting the diagram out of the editor
- Order jobs with dependencies (Builder)
- Scheduling and the run — the full reference for offsets, deadlines, retries and reruns
- Workflow Settings (Builder)
- Define a frequency (Builder)