Hey there! Let’s dive into your two Power Automate questions and get you sorted out.

If you’re looking for ways to trigger a flow specifically when a retention label is applied (and default triggers aren’t cutting it), here are some solid options:

• Scheduled monitoring with Recurrence trigger: Set up a flow that runs on a schedule (e.g., every 15 minutes) to check for files that recently had a retention label applied. Use the Get files (properties only) action with a filter query targeting the retention label metadata, then process any new matches.
• Microsoft Graph API integration: Use the Send an HTTP request to SharePoint action to call the Graph API and query files with retention labels. This gives you more control over exactly what you’re checking for, and you can pair it with a recurrence trigger to run checks periodically.
• Property-specific trigger: Instead of waiting for a label-specific trigger, use the When an item or file is modified (properties only) trigger. Retention label application often updates file metadata properties, so this trigger might catch the change where the standard "created or modified" one doesn’t.

Let’s troubleshoot why your current setup isn’t working:

• Double-check your condition column name: SharePoint columns sometimes have internal names that differ from their display names. For example, if your display name is "Item is a Record", the internal name might be something like ItemisaRecord. Go to your document library’s settings > Columns > select the column to find its internal name, then use that in your trigger’s condition.
• Confirm retention label application triggers a "modified" event: Some retention label operations don’t trigger the standard "modified" event because they only update backend metadata, not visible file properties. Test manually editing a file’s properties (like adding a comment) to see if the trigger fires—if it does, the label action isn’t triggering the event, and you’ll need to switch to the properties only trigger mentioned earlier.
• Check trigger scope and permissions: Make sure your trigger is set to include subfolders if your files are stored there. Also, verify the account connected to Power Automate has full access to the document library—without proper permissions, the trigger won’t detect changes.
• Debug with a test action: Temporarily remove the condition and add a Send me an email action as the first step in your flow. If you get the email when a file is modified, the issue is with your condition; if not, the trigger itself isn’t detecting changes, and you’ll need to re-authenticate your SharePoint connection or check for platform outages.

内容的提问来源于stack exchange，提问作者Ishit Vyas