How to Fix a Disconnected SharePoint Workflow Manager Farm

When your enterprise automation suddenly stops routing tasks and generating approvals, fixing a Disconnected SharePoint Workflow Manager Farm becomes your top administrative priority. A disconnected state typically occurs after server patching, service account password expirations, or backend database migrations. This guide explains the best diagnostic steps and restoration methods to bring your workflow infrastructure back online without data loss. Whether you are dealing with expired Service Bus certificates or a corrupted farm configuration, The sections below explain the most effective approaches to resolve the connection breakdown.

5 Ways to Fix a Disconnected SharePoint Workflow Manager Farm

1. Restore-WFFarm PowerShell Command

• It is the primary, Microsoft-supported disaster recovery cmdlet specifically designed to restore farm connectivity when nodes lose communication with the backend databases.
• Re-establishes the connection between the Windows Fabric, Service Bus, and the Workflow Manager databases using existing data.
• Preserves existing workflow instances and history; requires minimal reconfiguration compared to building a new farm.
• Requires exact knowledge of the original RunAs account credentials and certificate generation keys.

2. Re-registering the Service via Register-SPWorkflowService

• Often, the farm itself is healthy, but the SharePoint web application has lost its trusted connection to the workflow endpoint.
• Forces SharePoint to update its proxy connections and re-establish the OAuth trust with the Workflow Manager URI.
• Extremely fast to execute; does not require taking the Workflow Manager backend offline.
• Will not work if the underlying Service Bus is crashed or if the Workflow Manager IIS site is stopped.

3. Service Bus Certificate Renewal and Injection

• Expired auto-generated certificates are the leading cause of a disconnected state. This method directly addresses the root cryptographic failure.
• Uses the Set-SBCertificate and Set-WFCertificate cmdlets to generate and distribute new SSL and encryption certificates across the farm nodes.
• Permanently fixes SSL trust errors; prevents future disconnections for another 5 years (default lifespan).
• Highly complex sequential process; missing a single node update can completely break the Service Bus message broker.

4. Synchronizing Service Account Credentials

• Active Directory password policies often force changes to the Workflow Manager RunAs account, immediately disconnecting the farm from SQL Server.
• Updates the Windows Services (Workflow Manager Backend, Service Bus Gateway, Service Bus Message Broker) and the IIS Application Pools with the new AD password.
• Fixes authentication-driven disconnections without needing complex PowerShell recovery scripts.
• Requires a full service restart, causing temporary downtime for any remaining active background processes.

5. Complete Farm Rebuild (Keep Databases)

• When registry keys or Windows Fabric installations become irreparably corrupted, a clean rebuild pointing to existing databases is the practical fail-safe.
• Involves leaving the farm via the Workflow Manager Configuration Wizard, clearing the server, and joining a new farm using the existing SQL database names.
• Clears out deep-seated Windows Fabric corruption; helps ensure a clean installation state.
• Highly disruptive; highest risk of human error; time-consuming.

Compare Methods for Fixing a Disconnected SharePoint Workflow Manager Farm

Troubleshooting Method	Execution Difficulty	Downtime Required	Primary Root Cause Addressed
Restore-WFFarm Command	High	Moderate	Corrupted topology / Server loss
Register-SPWorkflowService	Low	None	Broken SharePoint OAuth trust
Certificate Renewal	Very High	High	Expired auto-generated certificates
Credential Synchronization	Low	Low	Expired Active Directory passwords
Farm Rebuild (Keep DBs)	Extreme	Very High	Irreparable Windows Fabric failure

FAQs About Fixing a Disconnected SharePoint Workflow Manager Farm

How do I verify the current status of my Workflow Manager connection?

Open the SharePoint Management Shell as an administrator and run Get-SPWorkflowServiceApplicationProxy. Check the output for the URI endpoint and ensure it accurately reflects your current Workflow Manager load balancer or server FQDN. Additionally, verify that the Status property does not return a disconnected or offline state.

Can a disconnected farm cause data loss for in-progress workflows?

Generally, no. In-progress workflows are serialized and stored in the SQL Server backend databases (WFInstanceManagementDB). Once you successfully apply a method on fixing a Disconnected SharePoint Workflow Manager Farm, the Windows Fabric will resume processing the queued messages from where it left off, provided the databases were not altered.

Which Windows services must be running for the farm to connect?

To ensure a healthy connection, verify via services.msc that the following are actively running: Workflow Manager Backend, Service Bus Gateway, Service Bus Message Broker, and Windows Fabric. If Windows Fabric is stuck in a 'Starting' state, the farm will remain disconnected.

Why does Register-SPWorkflowService return a 403 Forbidden error?

A 403 Forbidden error during re-registration typically means the SharePoint server does not trust the Workflow Manager's SSL certificate. You must export the public key of the Workflow Manager certificate and add it to the SharePoint Central Administration's Manage Trusts section before the command will succeed.

Edit Downloaded Files in WPS Office While SharePoint Is Repaired

Determining fixing a Disconnected SharePoint Workflow Manager Farm requires patience and a methodical approach to diagnosing SQL connections, OAuth trusts, and certificate validity. By following the top methods outlined above—ranging from a simple service re-registration to a full farm restore via PowerShell—administrators can bring enterprise automation back online safely.

Because these disaster recovery procedures involve complex PowerShell commands, unique passphrase keys, and specific database names, maintaining an accurate incident response document is critical. You can use WPS Office to create and securely store your SharePoint disaster recovery runbooks. With WPS Writer, you can organize complex PowerShell scripts using clear formatting, use its built-in PDF tools to distribute read-only recovery manuals to your IT team, and ensure that the exact parameters needed to fix your farm are always accessible during a crisis. Standardizing your IT documentation in WPS Office ensures your team is never left guessing when a critical infrastructure disconnection occurs.