How to Troubleshoot SharePoint Designer 2013 Workflow Service Errors
Question details
Users are encountering a "workflow service cannot be reached" error in SharePoint Designer 2013 that is not resolved by clearing the application cache or reinstalling the software.

- Product
- SharePoint Designer 2013
- Device & OS
- not provided
- Scenario
- Administrators are attempting to manage or fix workflows in a SharePoint 2016 on-premises environment.
- Observed behavior
- SharePoint Designer 2013 workflows stop functioning and display an error stating the workflow service cannot be reached, persisting even after client-side troubleshooting.
Ensure you have administrative access to the SharePoint 2016 environment and collect all relevant server logs and exact error messages before proceeding.
Escalate to Microsoft Support via the Admin Center
Since client-side fixes like clearing the cache or reinstalling Designer do not work, the issue requires a server-side investigation by Microsoft Support.
The "workflow service cannot be reached" error in a SharePoint 2016 on-premises environment usually indicates an issue with the Workflow Manager backend rather than the local SharePoint Designer client. Standard local troubleshooting will not resolve service-level disconnects.
Document your exact SharePoint 2016 on-premises topology, recent updates applied to the server, and the exact error message displayed in SharePoint Designer 2013.
Have your Microsoft 365 or SharePoint administrator log in to the Microsoft 365 admin center or the applicable volume licensing support portal.
Navigate to 'Help and support' to create a new service request. Clearly state that the issue is with an on-premises SharePoint 2016 environment using the SharePoint Designer 2013 workflow platform.
Inform the support engineer that reinstalling SharePoint Designer and clearing the local cache have already been attempted without success, directing their focus to the server-side Workflow Manager.

Document Your SharePoint Configurations with WPS Office
While troubleshooting complex server and workflow errors in SharePoint, you need a reliable office suite to log issues, draft standard operating procedures, and communicate with your team. WPS Office is a lightweight, free alternative that offers comprehensive productivity tools.
- 1. Download the installer: Visit the official WPS Office website and download the free installation package for your operating system.
- 2. Install the software: Run the installer and follow the on-screen prompts to set up WPS Office on your computer.
- 3. Open your documents: Launch WPS Office to instantly open your existing Microsoft Word, Excel, and PowerPoint files without formatting loss.

Frequently Asked Questions
Why didn't clearing the SharePoint Designer cache fix the workflow error?
Clearing the cache only resolves local synchronization or file corruption issues within the Designer client. A "workflow service cannot be reached" error typically means the actual backend Workflow Manager service on the SharePoint server has stopped, crashed, or become disconnected.
Can I resolve this error without contacting Microsoft Support?
If you are a SharePoint administrator, you can check the Workflow Manager backend services, IIS application pools, and event viewer logs on the server. However, if the service remains unreachable after server reboots and standard checks, escalating to Microsoft Support is highly recommended.
Is SharePoint Designer 2013 still supported for SharePoint 2016?
Yes, SharePoint Designer 2013 is the designated tool for creating and managing workflows in SharePoint 2016 on-premises environments, but it relies heavily on the server's Workflow Manager infrastructure functioning correctly.




