Skip to main content

Registry Health Check

Path: Monitoring → Automations → Registry Health Check

Registry Health Check inspects the integrity of the Trigger and Action catalog itself, platform wide, separate from any single workflow run. It confirms every module the system discovered is actually reachable, and that every saved workflow's nodes still point at triggers and actions that genuinely exist.

Opening Registry Health Check​

  1. Go to Monitoring → Automations.
  2. Click the Registry Health Check tab. Sits beside Execution History, just under the page title. A Run Health Check button replaces the Purge button in the top right while this tab is open.
  3. Click Run Health Check to re-run the scan. Updates the Checked at time shown in the summary banner below.

Reading the Summary​

  1. Read the banner at the top. States the overall finding in plain language, for example Stale Registry Configurations Detected, with a short explanation underneath.
  2. Read the four metric cards below it.
CardMeans
Discovered ModulesHow many modules the Trigger and Action catalog found, shown as a count out of itself, for example 11 of 11.
Healthy ModulesHow many of those discovered modules are actually reachable right now.
Schema WarningsA count of modules whose schema looks stale compared to the live CRM field mappings, without being fully broken.
Endpoint ErrorsA count of modules that could not be reached at all.

Registry Health Check tab showing a Stale Registry Configurations Detected banner, four metric cards reading Discovered Modules 11 of 11, Healthy Modules 11, Schema Warnings 0, Endpoint Errors 0, and a long Saved Workflows Health list mostly marked PASS with a few marked ERROR

Figure 1. Registry Health Check: every module reachable, zero schema warnings, zero endpoint errors, yet the banner still flags stale configurations, which Saved Workflows Health below it explains.

Checking Saved Workflows Health​

  1. Scroll to Saved Workflows Health. Lists every saved workflow by name and ID, each marked PASS or ERROR.
  2. Click an ERROR row to expand it. PASS rows are not expandable. Only rows marked ERROR, each also showing an error count badge such as 1 Errors, have the expand arrow.
  3. Read the exact error reason listed underneath.
warning

A real example: workflow 113 shows ERROR with an unrecognized Trigger ID. Its edit panel still opens, but nothing shows as selected.

Checking Registered Module Configurations​

  1. Scroll below Saved Workflows Health to Registered Module Configurations. Lists every module the catalog discovered, by its internal key, with its own Actions and Triggers counts and a PASS or ERROR status.
ModuleActionsTriggers
campaign115
ai50
statusManagement106
messaging91
users78
groups45
calls910
edge30
emailProvider21
config60
integrations10

An expanded ERROR row for New Lead Inbound Alert reading References unknown trigger ID on-leads-created, followed by the start of the Registered Module Configurations list showing modules such as campaign, ai, statusManagement, messaging, and users with their Actions and Triggers counts

Figure 2. A real expanded error, directly above the start of Registered Module Configurations.

warning

These are internal module keys, not Designer names. calls means Telephony here. CRM modules are counted separately, under their own categories.

tip

Run Health Check before assuming a node editor is broken. A stale reference just leaves nothing selected there.