Troubleshoot Sub-Account Workflow Errors Inside Workflow Maps

TL;DR

HighLevel updated Workflow Maps to surface execution errors across a sub-account in a single consolidated screen. Agency users and admins should check their sub-accounts to spot failed workflows without inspecting logs individually.

Who this affects

HighLevel has not confirmed the full scope of who is affected across all role types. However, access to Workflow Maps is restricted to agency users and agency admins at launch. Standard sub-account users without agency credentials cannot access it. HighLevel has not confirmed whether any plan gating or usage limits apply.

What changed

HighLevel added centralized error visibility and troubleshooting tools to Workflow Maps:

• Workflow Maps now displays workflow execution errors across an entire sub-account in one view.
• Any workflow that experienced errors during recent runs now displays an errors badge.
• Added a "Review workflows with errors" option that organizes flagged workflows into Published and Draft categories.
• Added a "Has issues" filter to narrow the Workflow Maps display strictly to workflows with problems.
• Clicking a workflow displays its failed executions, affected steps, and specific error details.
• Added a "Mark as read" action that clears the error badge without retrying the failed execution or modifying the workflow setup.
• Access to Workflow Maps is restricted to agency users and agency admins at launch.
• Rollout status, plan gating, and whether this replaces or breaks existing interfaces remain unconfirmed by HighLevel.

Where to find it

In your sub-account, navigate to Automation > Workflows > Workflow Maps. The new "Has issues" filter and "Review workflows with errors" options appear directly inside that screen.

How agencies will use this

An agency admin logs into a client sub-account and goes directly to Automation > Workflows > Workflow Maps to perform routine maintenance. Instead of opening individual workflows and clicking through separate execution logs, the admin applies the "Has issues" filter to hide healthy automations.

From the filtered map, the admin clicks "Review workflows with errors" to separate active issues in Published workflows from non-critical issues in Draft workflows. Selecting a flagged workflow opens a view showing the failed executions, the specific step where the failure occurred, and the technical error details. After noting the root cause, the admin can select "Mark as read" to dismiss the errors badge immediately, leaving the workflow and execution history intact without triggering an unwanted retry.

Our take

This is a significant functional update for agency technical leads and account managers. Workflow troubleshooting in HighLevel has traditionally required manual log checking across separate automations. Surfacing failures across an entire sub-account on one visual map cuts real diagnostic time. Just remember that "Mark as read" only clears the visual badge—it does not resolve the underlying issue or retry the run.