Skip to main content

Monitor the daily run

The Processes view is where you watch the day's automation run: which workflows are in progress, and which jobs are waiting, running, finished, or failed. Use it to step in when something needs attention.

What this solves

Without one place to watch the day's automation, a stalled or failed job goes unnoticed until a business process is already late.

Two ways to look at the run​

  • Workflow View: a list of workflow instances; open one to see its diagram of jobs, colored by status. Best for seeing the shape of a run and where it's blocked. Filter by status using simple groups (Building, Waiting, In Process, On Hold, Completed, Cancelled) to narrow to just the workflows you care about.
  • Job View: a filterable, sortable table of job instances. Best for finding specific jobs by name, status, or time.

Watch the run​

To monitor the run, complete the following steps:

  1. Go to Operations › Processes and select the environment you're monitoring.
  2. Use Workflow View to see workflows and their jobs, or switch to Job View to search and filter jobs.
  3. Select a job to open its detail: its output, a summary of the run, its configuration, its status history, and the actions its status allows.
  4. Use Refresh to pull the latest state.

From a job on the workflow diagram you can also jump to that job in Job View (View in Job View on the job's menu) to act on it.

Reading status at a glance​

Jobs move through waiting → running → finished states. A waiting job is usually fine. It's waiting on a dependency, its start time, a resource, an expression, or an agent. A job briefly in a completion-processing state is finishing, not stuck. Focus your attention on failed jobs and jobs running late. See Job statuses and actions.

Workflow View flags a workflow that has failed jobs. A failed job does not change its workflow's status, so the Status column adds a red "N failed" indicator beside the status of any workflow with failed jobs, and a finished workflow with failures reads Completed with errors rather than Completed. Open the workflow to find the failed jobs, or use Show jobs with errors in Job View. See Workflows with failed jobs.

The diagram tells you when a wait will not end on its own. A job held by a dependency that will not resolve until someone adds the predecessor — a required predecessor that is not in the run, or a multi-instance predecessor whose instance for this job's group is not in the run yet — carries a yellow warning icon, and its tooltip names the predecessor and the reason. A waiting job without that icon is waiting on something that can still arrive. The diagram also draws the thresholds, resources and expressions jobs are waiting on as their own cards, so you can see what is holding a run without opening each job. See Dependencies on the diagram.

A job waiting to start may be one that is failing

A job whose frequency configures failure retries does not read Failed while it has attempts left. Between attempts it waits in Wait Start Time — the same state as a job waiting for its scheduled start — still holding the failed attempt's exit code. So a job that keeps failing can look like one that simply hasn't started. If a waiting job shows an exit code, check Retry Count on its Summary tab before assuming it is fine. See Respond to a failed job.

Start a workflow manually​

Use the Schedule Workflow action to run a workflow outside its normal schedule. Choose the workflow and the schedule date, or a range of up to 31 dates.

Related topics