Skip to main content

Acting on runs in Processes

In briefFrom Processes you act on the run: you schedule a workflow into it, act on one job or workflow instance or on several at once, add a job defined on the workflow to an instance that is already running, and correct a job on a run under way. An edit changes that instance only, until you promote it to the workflow with Push Changes to Workflow.

WhereOperations › Processes (see The Processes page (runtime)). Schedule Workflow is on the page. Each row has an action menu, and a Bulk actions button appears once two or more rows are selected. Add Job and Job Actions are in a workflow instance's row menu in Workflow View. The job editor opens from Edit Job on a job's node in the workflow diagram, and Push Changes to Workflow sits in its footer.

When

  • You need to act on one job or workflow instance, or on several at once, or on every job in one workflow instance.
  • You want to schedule a workflow into the run, for up to 31 days in one pass, or add a job defined on the workflow to an instance that is already running.
  • You need to correct a job on a run under way, and possibly promote that edit to the workflow.

Use something else when you only need to read the run, filter it, or open a job's detail and output: see The Processes page (runtime). When you need to know what a status or action means, see Job and workflow statuses.

How

  1. Open Operations › Processes, and check the environment above the page.
  2. Use a row's action menu for one job or workflow instance, or select two or more rows and use Bulk actions, which offers only the actions every selected row accepts. To change every job in one workflow instance, use Job Actions in its row menu in Workflow View.
  3. To add a job to a running instance, open Add Job from the instance's row menu in Workflow View.
  4. To correct a job on a run under way, open Edit Job on its node in the workflow diagram. Use Save for this instance, and Push Changes to Workflow when every future build needs a change to its task settings, tags or custom fields too.

For the full steps, see Work the Processes page.

Notes
  • Changing page, sort, search or a filter clears the row selection, so a bulk action never acts on rows you cannot see.
  • Job Actions on a workflow instance changes only the jobs whose status allows the action, and reports how many it skipped and why.
  • An edit in the job editor changes this instance only. Push Changes to Workflow writes the task settings, tags and custom fields to the workflow definition as a new version, and nothing else. A container job's Sub-Workflow cannot be changed on an instance.
  • A Success Reruns change is refused on a finished job that nothing will run again (turning reruns off is accepted), on Restart Offset with neither Maximum Runs nor a latest runtime, and when new instance times or a new latest start time would put the next rerun or failure retry past the latest start. Maximum Runs can be cleared on an instance.
  • Each action needs its permission in the workspace of the workflow the instance was built from. See Who can do what on Processes.
Watch out
  • Kill stops the process only on a legacy (LSAM) agent. On a Universal Agent the process keeps running.
  • One tick of Overwrite Existing applies to every date in the range. Read the count in the confirmation first.
  • Hold, Release and Start on a completed workflow reopen it. Read the Reopen Completed Workflow confirmation first.