SharePoint 2013 Workflow Problems: Current Scope and Safe Checks

If a SharePoint 2013-platform workflow fails, establish the hosting model before troubleshooting. SharePoint 2013 workflows in SharePoint Online were fully retired on 2 April 2026. An Online tenant cannot repair or extend that retired service. Supported on-premises farms use SharePoint Workflow Manager and need a different diagnostic path.

The words “SharePoint 2013 workflow” describe a workflow platform, not necessarily a SharePoint Server 2013 farm.

SharePoint Online: stop repairing and migrate

Microsoft's retirement notice says SharePoint 2013 workflow was removed from existing tenants on 2 April 2026, with no extension option.

For SharePoint Online:

inventory workflows and their business owners
identify triggers, actions, credentials and dependencies
decide whether to rebuild in Power Automate or another supported orchestration product
test the replacement with real permissions and exception cases
retain the old workflow definition and run history required by your records policy

Do not promise a one-click conversion. A workflow's visible steps may hide custom actions, impersonation, email assumptions or state stored outside the workflow.

SharePoint Server: use SharePoint Workflow Manager

Microsoft provides SharePoint Workflow Manager for supported on-premises SharePoint Server versions. The older Microsoft Workflow Manager and Service Bus products should not be treated as the current target architecture.

Before changing the farm, collect:

SharePoint and Workflow Manager versions
topology and service-account details
workflow endpoint URL and protocol
certificate chain and expiry
the site collection used for registration
correlation IDs, ULS logs and Workflow Manager event logs
recent farm, certificate, DNS or proxy changes

Take supported backups and use a non-production reproduction where possible.

Check 1: validate the endpoint from both sides

Microsoft's upgrade and certificate guidance uses the Workflow Management endpoint on the Workflow Manager server, then validates access from SharePoint servers. A service that answers locally but not from SharePoint points to a network, TLS, trust, proxy or name-resolution boundary.

Do not “fix” an HTTPS problem by adding -AllowOAuthHttp unless the design explicitly and safely uses HTTP. Microsoft documents separate registration paths for HTTP and HTTPS.

Check 2: inspect registration

Use:

Get-SPWorkflowConfig -SiteCollection "https://sharepoint.contoso.com/sites/workflows"

Compare the registered workflow host URI with the intended endpoint. If registration is wrong, preserve the current output and follow Microsoft's installation and configuration procedure for the actual protocol and certificate model.

Blindly unregistering and re-registering can widen the incident.

Check 3: validate certificates

Expired or untrusted certificates can break communication even when services are running. Microsoft's certificate installation guidance says the required certificates must be installed on SharePoint servers.

Check the full chain, names, expiry, private-key access where required and trust on every participating server.

Check 4: separate platform health from one bad workflow

If every 2013-platform workflow fails, investigate endpoint, registration, certificates, services and farm health.

If one workflow fails, inspect its own history, list permissions, custom actions, payload and changed dependencies. Do not rebuild the workflow farm to repair a single malformed definition.

Check 5: prove the repair

Test:

endpoint access from each SharePoint server
a small known-good workflow
the affected workflow with a controlled item
expected updates, email and error handling
restart behaviour and duplicate prevention
logs with no new related errors

A workflow reaching “Completed” proves that one run completed. It does not prove every branch, permission context or production dependency works.

Sources

For practical migration and SharePoint admin discussions, join the SharePoint & Teams Admins Space.