Fix SharePoint Designer Workflow Status Stuck on Starting
Question details
Users are experiencing an issue where SharePoint 2016 workflows created via SharePoint Designer 2013 fail to execute and hang indefinitely upon triggering.

- Product
- SharePoint Server 2016
- Device & OS
- not provided
- Scenario
- Adding new list items that are expected to trigger an automatic email workflow on an on-premises SharePoint farm.
- Observed behavior
- The workflow status remains stuck at "Starting" and completely fails to send the automatic emails to users.
Ensure you have farm administrator privileges to access SharePoint Central Administration, server services, and ULS logs before attempting to troubleshoot this issue.
Troubleshoot On-Premises SharePoint Workflow Services
Verify the configuration of essential workflow components such as timer jobs, service accounts, and outgoing email settings.
Workflows sticking at the "Starting" status on an on-premises SharePoint Server usually indicate an underlying communication issue with the Workflow Manager, stalled timer jobs, or insufficient permissions for the workflow service account.
Navigate to the affected list item, click on the workflow status column (which says "Starting"), and review the hidden workflow history logs for any immediate error codes or messages.
Open SharePoint Central Administration, go to Monitoring, and select "Review job definitions". Ensure that the Workflow Auto Cleanup and related workflow timer jobs are actively running and not stuck or failing.
Confirm that the service account running the SharePoint Workflow service has the necessary Read/Write permissions to access the specific list and is authenticated to send emails.
In Central Administration, navigate to System Settings and click "Configure outgoing e-mail settings". Check if the SMTP server is reachable, correctly spelled, and properly configured to relay emails from the SharePoint farm.
Access the SharePoint server and use the ULS Viewer tool to inspect the real-time logs. Filter by the correlation ID associated with the workflow failure to pinpoint the exact backend error.

Seek Advanced Support from Microsoft Communities
Since on-premises SharePoint Server troubleshooting falls outside standard Microsoft 365 support, escalate the issue to specialized Microsoft forums.
Looking for a Lightweight and Free Office Alternative? Try WPS Office
While WPS Office does not manage on-premises SharePoint servers, it serves as a highly compatible, free alternative to Microsoft Office for your daily document creation, editing, and team collaboration needs.
- 1. Visit the Official Website: Go to the official WPS Office website on your computer.
- 2. Download the Installer: Click the 'Free Download' button to get the latest lightweight installer for your operating system.
- 3. Install and Edit: Run the installer, set up your account, and instantly start creating and editing your documents for free.

Frequently Asked Questions
Why do SharePoint 2013 workflows get stuck on 'Starting' in SharePoint 2016?
This usually happens due to issues with the underlying Workflow Manager, stalled SharePoint timer jobs, insufficient service account permissions, or improper SMTP configuration that prevents the workflow from executing its initial steps.
Does this workflow hanging issue affect SharePoint Online?
No, this specific issue involving farm-level timer jobs and ULS logs typically applies only to SharePoint Server on-premises environments, such as SharePoint 2016.
Can a stuck SharePoint workflow be restarted manually?
Yes, a user with appropriate permissions can sometimes terminate the stuck workflow instance from the list item's workflow settings page and manually initiate a new instance to see if it bypasses the system hang.




