Others

How to Fix Power Automate Flow Entity Does Not Exist in SharePoint

Olivia Miller Oct 9, 2026 869 views

Question details

The user needs to fix an intermittent error where a Power Automate flow cannot be found when launched from a custom SharePoint button.

How to Fix Power Automate Flow Entity Does Not Exist in SharePoint

Product: Microsoft Power Automate and SharePoint
Device & OS: not provided
Scenario: Triggering a Power Automate workflow using the executeFlow custom row action within a SharePoint document library.
Observed behavior: The flow executes successfully when tested directly in Power Automate, but intermittently returns a 'Flow entity with name <Flow-ID> does not exist in the store' error when triggered via the SharePoint library button.

Before you start

Ensure you have Site Owner or Full Control permissions in the SharePoint site, and verify that your account has Edit privileges for the associated Power Automate flow.

Solution 1Recommended

Verify Flow Configuration and JSON Syntax

Ensure the flow is active, properly connected, and that the Flow ID in your SharePoint formatting perfectly matches the actual flow.

The most common cause of this error is a mismatch between the Flow ID referenced in the SharePoint JSON and the actual Flow ID, or the flow being disabled.

Check flow status

Log into Power Automate, locate your flow under 'My flows', and verify that its status is set to 'On'.

Verify SharePoint connections

Open the flow in Edit mode, check the SharePoint trigger and action connections, and ensure they are authenticated to the correct site and library.

Validate the Flow ID in JSON

Copy the Flow ID from the Power Automate URL (the alphanumeric string following '/flows/'). Go to your SharePoint library, edit the column formatting, and ensure the "id" attribute in the executeFlow action exactly matches this string.

Verify Flow Configuration and JSON Syntax

Ownership Warning: If the flow was created by another user, verify that it has been explicitly shared with you or the SharePoint site group so it can be executed.

Solution 2

Recreate or Republish the SharePoint Button Action

Refreshing the column formatting can resolve issues caused by moved, renamed, or replaced flows.

Solution 3

Seek Advanced Community Support

For persistent intermittent failures, consulting developer communities can help identify backend or timing-related anomalies.

Free Microsoft Office alternative

Need a Lightweight Alternative for Everyday Office Tasks? Try WPS Office

While WPS Office doesn't replace complex SharePoint or Power Automate enterprise architectures, it serves as a highly efficient, lightweight, and free Microsoft Office alternative for your everyday document, spreadsheet, and presentation needs. Avoid complex licensing and enjoy a familiar interface.

1. Visit the official website: Go to the WPS Office official website to access the download page.
2. Download and install: Click the Free Download button for your operating system and follow the standard installation prompts.
3. Open your files: Launch WPS Office and open your existing Microsoft Office files directly with full formatting preserved.

Free and lightweight office suite for Windows, Mac, and LinuxHigh compatibility with Microsoft Word, Excel, and PowerPoint formatsIntuitive tabbed interface for managing multiple documents easilySeamless transition with a familiar user experience

Frequently Asked Questions

Why does the executeFlow action say the flow doesn't exist?

This error generally occurs if the Flow ID in your SharePoint JSON formatting doesn't perfectly match the actual flow, if the flow is turned off, or if the user clicking the button lacks the necessary permissions to run the flow.

Where can I find the correct Flow ID for my JSON formatting?

You can find the correct Flow ID in the web browser URL when editing your flow in the Power Automate portal. It is the alphanumeric string immediately following '/flows/'.

Does renaming a flow change its Flow ID?

No, simply renaming a flow keeps the same ID. However, if you export a flow and import it as a new flow, a brand new Flow ID is generated, which must then be updated in your SharePoint JSON.

Office Quick Solutions