Workflow Health Status and Alerts
Harmony automatically monitors the resources that each workflow depends on and alerts you when something breaks. If a dataset, desk, catalog item, approver employee, or any other linked resource is deleted or an approver is terminated, the affected workflow is immediately flagged as unhealthy - so you can find and fix problems before they prevent a workflow from running correctly.
This article explains how health statuses work, what triggers an unhealthy state, and where to find health information in the UI and activity log.
How Workflow Health Monitoring Works
Every workflow in Harmony can depend on one or more external resources, such as:
Datasets - used to source or route work
Desks - used to assign tasks to a team or queue
Catalog items - referenced as part of a workflow step
Approver employees - designated to review or approve work items
Harmony continuously checks whether these resources are still available and valid. When all dependencies are intact, the workflow has a Healthy status. When one or more dependencies are broken, the workflow is marked as Unhealthy.
This monitoring runs automatically - you do not need to configure it or turn it on.
What Triggers an Unhealthy Status
A workflow is marked unhealthy when any of the following occurs:
A linked dataset is deleted
The dataset feeding a workflow step no longer exists
A linked desk is deleted
The desk assigned to receive tasks has been removed
A catalog item is deleted
A step references a catalog item that no longer exists
An approver employee is terminated
A designated approver is no longer an active employee
Any one of these conditions is enough to flag the workflow as unhealthy, even if all other dependencies are intact.
Viewing Health Status in the UI
Workflows with broken dependencies are clearly marked in the workflow list and workflow detail views with a health indicator. The indicator shows:
What is wrong - the type of dependency that is broken
Which resource is affected - the specific dataset, desk, catalog item, or employee that caused the issue
This lets you immediately understand the problem without having to investigate each step manually.
Finding Unhealthy Workflows
Navigate to Workflows in the main menu.
Look for workflows marked with the unhealthy indicator in the list.
Select a workflow to open its detail view and see the full breakdown of which dependency is broken.
Workflow Activity Log and Audit Trail
Every health status change is recorded in the workflow's activity log. This gives you a full audit trail that includes:
When the workflow became unhealthy
Which resource change triggered the status update
When the workflow was restored to a healthy state (after the issue is resolved)
To view the activity log, open the workflow detail view and go to the Activity tab. You can use this log to understand the history of any health changes and demonstrate compliance or investigate disruptions.
Resolving an Unhealthy Workflow
To restore a workflow to a healthy state, you need to address the broken dependency. Depending on the cause, this may involve:
Replacing a deleted resource - assign a new dataset, desk, or catalog item to the affected workflow step
Updating an approver - replace a terminated employee with an active approver in the workflow configuration
Once the broken dependency is resolved and all required resources are valid again, the workflow health status returns to Healthy and the change is recorded in the activity log.
Summary
Healthy
All dependencies are intact and the workflow can run correctly
Unhealthy
One or more dependencies are broken and the workflow may not run correctly
Workflow health monitoring is always on, requires no setup, and ensures that broken dependencies are surfaced immediately - so your team can act quickly and keep workflows running without interruption.
Last updated
Was this helpful?