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.
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 diagram of each workflow instance and its 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, Held, 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:
- Go to Processes and select the environment you're monitoring.
- Use Workflow View to see workflows and their jobs, or switch to Job View to search and filter jobs.
- Select a job to open its detail: status, timing, dependencies, output, and logs.
- Use Refresh to pull the latest state.
From the workflow diagram you can also jump to the matching jobs in Job View to act on them.
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.
The diagram tells you when a wait will never end. A job held by a dependency that cannot resolve — a required predecessor that is not in the run, or one that resolved to the wrong instance — carries an orange 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 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.
Related topics
- Respond to a failed job (Operator)
- Job statuses and actions (Operator)