Hi @DylanStout 

Please find below my findings for this issue. 

• No governed tags in scope: If there are no Unity Catalog governed tags defined or applied to objects visible to your current privileges, the UI can fail to populate the dropdown values for Tag. Verify that at least one tag exists and is applied to any visible object (catalog, schema, table, column, model, etc.).

• Privilege gaps: Loading tag values requires you to have visibility on objects carrying those tags. If you don’t have USE CATALOG/USE SCHEMA or VIEW METADATA on the objects, the filter may show “failed to load values.” Check you can see the tagged objects’ metadata and that you (or your group) have APPLY TAG/VIEW privileges where needed.

   

  Confirm at least one governed tag exists in your metastore and is applied to an object you can see:

  • In a SQL session: SHOW TAGS; and SHOW TABLE EXTENDED LIKE ... to inspect tags, or view an object’s details in Catalog Explorer to see applied tags.

    Verify permissions:

    • Ensure you have at least VIEW/USE privileges on objects expected to have tags; otherwise tag values won’t enumerate for you in the filter.

       

      Try a different scope:

      • Switch to a catalog/schema you know contains tagged objects and retry the Tag filter to see if values load there.
• Hard refresh / alternate compute:

Can you show that this filter is working from your side?

Yes, I'm an admin of the workspace, also, owner of the catalog, and able to see the tags

Hello @DylanStout!

Did the suggestions shared above help resolve your concern? If so, please consider marking the response as the accepted solution.
If you found a different approach that worked, sharing it would be helpful for others in the community.