Others

Fix Power Automate Flow Timeout When Modifying SharePoint Item

Aamir Naveed AkramAamir Naveed Akram Nov 3, 2026 869 views

Question details

The user needs to resolve an issue where a Power Automate flow hangs and times out during testing when triggered by a modified SharePoint item.

Fix Power Automate Flow Timeout When Modifying a SharePoint Item
Product
Power Automate / SharePoint
Device & OS
not provided
Scenario
Testing a flow that is supposed to send an email from a shared mailbox whenever an existing item in a SharePoint list is modified.
Observed behavior
The flow hangs indefinitely during the testing phase and ultimately reports that the starting action was not performed.
Before you start

Verify that your SharePoint list permissions are fully active and that the associated shared mailbox has not had any recent credential or access changes.

Solution 1Recommended

Recreate the Flow from an Official Template

Rebuilding the flow from scratch can resolve issues caused by a corrupted, stuck, or broken trigger path in the original automation.

Sometimes backend updates or temporary service glitches can corrupt a flow's trigger path, causing it to hang and fail to recognize when an item is modified. Recreating the flow completely refreshes the connection to the SharePoint environment.

1
Delete or Disable the Original Flow

Navigate to 'My flows' in Power Automate, locate the hanging flow, click the three dots (More commands), and select 'Turn off' or 'Delete'.

2
Create a New Flow from a Template

Click on 'Templates' in the left sidebar and search for the official template titled 'Send an email from a shared mailbox when an existing SharePoint item is modified'.

3
Configure Site and List Details

Select the template and connect your accounts. Enter your specific SharePoint Site Address and List Name in the trigger configuration.

4
Set Up the Shared Mailbox

In the email action node, enter the 'Original Mailbox Address' (the shared mailbox) and configure the recipient, subject, and body of the email.

5
Save and Test the Flow

Save the new flow. Click 'Test' in the upper right corner, choose 'Manually', and modify a test item in your SharePoint list to ensure the flow triggers successfully without timing out.

Recreate the Flow from an Official Template
Testing Alternative Environments: If the newly created flow still times out, configure it temporarily with a different SharePoint site and list. This helps determine if the issue is isolated to a specific list's configuration rather than the flow itself.
Free Microsoft Office alternative

Enhance Your Productivity with WPS Office

While you are troubleshooting Microsoft Power Automate and SharePoint issues, consider streamlining your everyday document tasks with WPS Office. It is a robust, lightweight, and highly compatible alternative for Word, Excel, and PowerPoint files.

  1. 1. Download the Installer: Visit the official WPS website and click the download button to get the free installation package.
  2. 2. Install WPS Office: Run the downloaded file and follow the quick setup wizard to install the software on your device.
  3. 3. Open Your Office Documents: Launch WPS Office and instantly open your existing Word, Excel, or PowerPoint documents without losing formatting.
Seamlessly open, edit, and save Microsoft Office formats (DOCX, XLSX, PPTX).Free, lightweight application that loads quickly and uses minimal system resources.Familiar tabbed interface that makes switching from Microsoft Office completely effortless.Built-in PDF editing tools for comprehensive document management.
microsoft office alternative - wps office

Frequently Asked Questions

Why does my Power Automate flow say the starting action was not performed?

This error typically indicates that the trigger (such as a SharePoint item being modified) was never successfully registered by Power Automate. This can be caused by a corrupted connection, revoked permissions, or a temporary outage in Microsoft's backend services linking SharePoint to Power Automate.

How can I tell if the timeout issue is specific to my SharePoint list?

You can isolate the issue by creating a brand-new test flow connected to a completely different SharePoint site and list. If the test flow works perfectly on the new list but fails on the original one, the issue lies within the original list's settings or column configurations.

Do I need to rebuild complex flow actions if only the trigger is broken?

If you have a very complex flow, you can try deleting just the SharePoint trigger action and adding it back instead of starting completely from scratch. However, if the flow still hangs after replacing the trigger, recreating it entirely from an official template is the most reliable fix.