Others

How to Fix SharePoint Workflows Not Working on a Specific Office 365 Site

WPS Editor Sep 25, 2026 869 views

Question details

The user needs to troubleshoot and resolve an issue where SharePoint workflows fail to start and time out on a single Office 365 site, while working normally on other sites.

How to Fix SharePoint Workflows Not Working on a Specific Office 365 Site

Product: SharePoint Online
Device & OS: not provided
Scenario: Attempting to execute SharePoint workflows via the web interface or a PowerShell script on a specific Office 365 site.
Observed behavior: Workflows fail to start, the workflow status remains blank, the workflow.aspx page times out, and PowerShell returns an 'Exception calling ExecuteQuery with 0 argument(s): The operation has timed out' error.

Before you start

Confirm that the issue is truly isolated to a single site by testing workflows on a different site within the same Office 365 tenant, and ensure you have Site Collection Administrator permissions to view workflow history.

Solution 1Recommended

Investigate Site-Specific Workflow Settings and History

Since the issue is isolated to one site, focus on checking the site's specific workflow configurations, lists, and history rather than tenant-wide services.

A localized workflow failure often points to corrupted list data, permission issues, or bloated workflow history specifically tied to the affected site.

Check workflow settings

Navigate to Site Settings > Workflow Settings on the affected site to verify the workflows are correctly associated with the appropriate lists and have not been accidentally suspended.

Review workflow history

Open the hidden Workflow History list on the site to check for specific error messages, unexpected termination events, or infinite loops that could be causing the timeouts.

Verify list permissions

Ensure that the user or service account initiating the workflow (and the PowerShell script) has the required read and write permissions on the site, lists, and individual items.

Test a basic workflow

Create and run a simple, out-of-the-box workflow (such as a basic approval) on a brand new test list within the same site to determine if the workflow engine responds at all.

Investigate Site-Specific Workflow Settings and History

Hidden List Access: You can access the hidden Workflow History list by appending '/Lists/WorkflowHistory' to your site's URL.

Solution 2

Escalate Unresponsive Sites to Microsoft 365 Support

If local troubleshooting fails and PowerShell ExecuteQuery timeouts persist, the underlying server infrastructure may require Microsoft's intervention.

Free Microsoft Office alternative

Looking for a Lightweight Alternative to Office 365?

While complex SharePoint workflows and Office 365 site management can sometimes lead to unexpected server timeouts, your everyday document creation shouldn't be complicated. WPS Office provides a free, lightweight, and highly compatible suite for all your offline and local document needs.

1. Visit the Official Website: Go to the official WPS website to access the secure, free download.
2. Download the Installer: Click the 'Free Download' button to get the lightweight installation file for your operating system.
3. Install and Start Creating: Run the installer and follow the simple on-screen instructions to start using your seamless Office alternative.

Highly compatible with Microsoft Office formats including .docx, .xlsx, and .pptx.Lightweight installation that doesn't bog down your system.Familiar user interface allowing for seamless migration and zero learning curve.Free to use with comprehensive word processing, spreadsheet, and presentation tools.

microsoft office alternative - wps office

Frequently Asked Questions

Why do SharePoint workflows time out on only one site?

A site-specific timeout usually indicates an issue with that particular site's data structure, such as a massive list exceeding the view threshold, corrupt workflow history, or an infinite loop within a custom workflow.

What does the PowerShell 'ExecuteQuery' timeout error mean in SharePoint?

This error occurs when a PowerShell script sends a request to the SharePoint server using CSOM, and the server fails to process and respond within the default timeout limit. This is often caused by querying too many items at once or server-side performance degradation.

How can I fix the workflow.aspx page not loading?

If the workflow.aspx page times out or fails to load, check if the workflow history list is bloated. If it contains millions of items, cleaning it up can resolve page load issues. Alternatively, temporarily disable custom scripts that might be conflicting with the page load.

Office Quick Solutions