Skip to content
Mango9

Workflow Runs

See what happened when a workflow ran and where a follow-up needs attention.

In the CRM: Workflows → All Workflows → workflow menu → View Jobs

Follow an enquiry through the process

A job is one run of a workflow. Open the workflow’s three-dot menu and choose View Jobs, or choose View Jobs while editing a saved workflow.

The screen shows Completed, Failed, Active/Pending and Total Runs, followed by individual jobs with their status, current step, start time, completion time and error text.

Illustration using the current native run-history view with fictional records and an example error. These are not customer runs. Select the image to enlarge it.

Read the status

Read the status
StatusWhat to do next
PendingThe run has been queued. Check again for progress.
RunningThe workflow is processing its steps.
WaitingCheck the workflow’s delay or pending result before expecting the next action.
CompletedThe workflow finished. Check the related message, task or call record for its own outcome.
FailedRead Error and check the settings of the indicated step.
CancelledThe run was stopped before normal completion.

Resolve the right part of the process

The screen displays the most recent 50 jobs. Hover over shortened Error text to read the full message. A completed workflow is a process result; SMS delivery and a customer’s appointment attendance have their own records.

  1. Identify the job and its Step, then open the workflow and find the corresponding action.
  2. For a message step, check the sender, recipient and message or template. For email, also check the selected SMTP connection.
  3. For an AI call, check the chosen outbound agent, its number, call history and recorded result.
  4. For a staff task or assignment, check the staff choice, deadline and time zone. For a condition, check the comparison and both destinations.
  5. Save the correction and review a controlled event before using the workflow for a larger campaign.

Test without contacting the wrong person

The editor’s Test Run executes real workflow actions using the account’s first contact automatically. Use it in a test account where that contact and all message or call destinations belong to you.

For a live business workflow, trace a known event through View Jobs and the relevant CRM record. This helps you distinguish an event that never started a run from a run that started and stopped at a particular step.