Local Cluster Troubleshooting v2

Use this checklist when a Workflow cannot select, save, Debug, publish, or run on a local Cluster.

An invalid Cluster is specified

Confirm the Cluster belongs to the current Site and is visible to your Cluster permissions. Refresh Local Clusters and the designer after creating or changing it.

Node or Connection is incompatible

The entire Workflow must run on one Cluster. Inspect every Node Method and selected Connection. A cloud-only contract or Connection assigned to another Cluster can prevent selection or execution.

Move incompatible work behind a separate Workflow and call it via Sub-Workflow, or use a compatible Node and Connection.

Cluster is offline

Open Local Clusters and confirm at least one Host is online. On each affected Windows Host:

Open Flowgear Local Cluster Manager and confirm that the configuration shows Complete and the Service badge shows Running. A running service does not by itself confirm that the Host has connected.
Check outbound TCP 443, DNS, proxy, and certificate trust.
Confirm the configuration contains the current Tenant Host, SiteKey, and ClusterKey.
Click Open Log Folder in the app to review the local runtime logs, and check Windows Event Viewer.

Certificate or authentication fails

Compare the CertificateThumbprint in the Host's configuration in Flowgear Local Cluster Manager with the trusted thumbprint in the Cluster's Certificate section in Console.

If no certificate is trusted, click Configure & Start in the app to send the certificate, and then trust the matching entry under Candidate certificates. See Local Cluster - Setup.
If a candidate shows Expired, click Configure & Start again to submit it again.
If the app reports that the certificate was not accepted, the Cluster already has a trusted certificate or holds five candidates. Remove the certificate or unneeded candidates in Console.
If the thumbprints differ on a Host you added, import the trusted certificate with its private key on that Host. Every Host in a Cluster uses the same certificate. See Add a Host to an existing Cluster.

Do not upload a private .pfx as the Cluster trust certificate.

After trusting or replacing a certificate, click Restart Service in the app and confirm a fresh Host heartbeat.

Version or update mismatch

Compare Host Versions on the Cluster detail page. Download the current installer and update Hosts one at a time when high availability matters. Confirm the service is running after each in-place upgrade.

Workflow still will not run

Confirm publish, Environment status, Connection values, Host capacity, trigger routing, and Sub-Workflow placement. Use Workflow logs to distinguish dispatch failure from a Step failure on the local Host.