Others

How to Fix Power Automate Error: GUID Does Not Exist in Term Store

Algirdas JasaitisAlgirdas Jasaitis Nov 2, 2026 868 views

Question details

The user needs to resolve an error in Power Automate where a specified GUID is reported as missing from the term store during file property retrieval.

How to Fix Power Automate Error: GUID Does Not Exist in Term Store
Product
Power Automate and SharePoint
Device & OS
not provided
Scenario
Using the 'Get files (properties only)' action in a flow that interacts with a SharePoint library containing managed metadata columns.
Observed behavior
The Power Automate flow fails and returns an error stating that a given GUID does not exist in the SharePoint term store.
Before you start

Ensure you have SharePoint site admin permissions and can access the Term Store Management Tool to verify metadata configurations before modifying your flow.

Solution 1Recommended

Verify and Update SharePoint Term Store GUIDs

Check the SharePoint Term Store to ensure the managed metadata term referenced by the failing file still exists and matches the expected GUID.

This error typically occurs when a SharePoint list item is tagged with a managed metadata term that was later deleted or recreated in the Term Store. Power Automate attempts to read the old GUID, which no longer exists.

1
Access the Term Store

Go to your SharePoint Admin Center, expand 'Content services', and select 'Term store'.

2
Locate the problematic term

Navigate through your taxonomy to find the term set associated with the managed metadata column used in your SharePoint list or library.

3
Check term GUIDs

Select the terms and check their Unique Identifiers (GUIDs) in the properties panel to see if they match the missing GUID from your Power Automate error log.

4
Reassign metadata

If the term was deleted, navigate to the specific file in your SharePoint library, clear the invalid metadata field, and re-tag it with a valid, existing term.

Verify and Update SharePoint Term Store GUIDs
Hidden Taxonomy List: Sometimes the SharePoint hidden taxonomy list retains orphaned terms. Re-tagging the item directly in SharePoint forces the list to update its references.
Free Microsoft Office alternative

Looking for a Hassle-Free Office Suite? Try WPS Office

While automated workflows in Microsoft Power Automate and SharePoint are powerful, they can sometimes lead to complex troubleshooting. If you need a reliable, lightweight, and completely free alternative for your daily document creation and editing needs, WPS Office offers a seamless experience with full format compatibility.

  1. 1. Download the installer: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install the software: Run the downloaded installation file and follow the on-screen prompts to set up the suite.
  3. 3. Open your files: Launch WPS Office and easily open, edit, and save any existing Microsoft Office documents without format loss.
Free and lightweight office suite for Windows, Mac, and mobileFully compatible with Microsoft Word, Excel, and PowerPoint formatsBuilt-in PDF editor and powerful toolkit for daily productivityUser-friendly interface that requires zero learning curve for seamless migration
microsoft office alternative - wps office

Frequently Asked Questions

What is a GUID in the SharePoint Term Store?

A GUID (Globally Unique Identifier) is a unique string of characters assigned to every term and term set within the SharePoint Term Store. Power Automate uses these GUIDs to accurately reference and retrieve metadata.

Why does 'Get files (properties only)' fail with managed metadata?

This action often fails if a file in the SharePoint library is tagged with a managed metadata term that has since been deleted or replaced in the Term Store. The flow tries to read the associated GUID, realizes it is missing, and triggers an error.

Can I ignore metadata columns when getting files in Power Automate?

Yes, you can use OData filter queries in the 'Get files (properties only)' action or create a specific SharePoint view that excludes the problematic managed metadata columns, allowing your flow to bypass the broken GUID references.