Describe the business value of Microsoft Power Platform →hardMultiple ChoiceObjective-mapped

Why Your Power Automate Flow Doesn't Trigger on a SharePoint Folder

Exhibit

{
  "flows": [
    {
      "name": "Approval Flow",
      "triggers": [
        {
          "type": "When a file is created in SharePoint",
          "site": "https://contoso.sharepoint.com/sites/ExpenseReports",
          "folder": "Pending"
        }
      ],
      "actions": [
        {
          "type": "Start an approval",
          "assignedTo": "manager@contoso.com",
          "item": "@{triggerOutputs()?['headers/{Filename}']}"
        },
        {
          "type": "Condition",
          "expression": "@equals(outputs('Start_an_approval')?['status'], 'Approved')",
          "ifTrue": [
            {
              "type": "Move file",
              "to": "Approved"
            }
          ],
          "ifFalse": [
            {
              "type": "Move file",
              "to": "Rejected"
            }
          ]
        }
      ]
    }
  ]
}

Refer to the exhibit. A Power Automate cloud flow is configured to move files in a SharePoint document library based on approval status. The flow triggers when a file is created in the 'Pending' folder. However, when a file is uploaded to the 'Pending' folder, the flow does not trigger. What is the most likely cause?

Quick Answer

The answer is that the flow is configured to trigger on file creation in the root of the document library, not the 'Pending' folder. This is because Power Automate’s “When a file is created” trigger defaults to monitoring the top-level library unless you explicitly set the folder path to the specific subfolder; without that path, any file uploaded to a subfolder like 'Pending' is invisible to the trigger. On the PL-900 exam, this tests your understanding of trigger scoping—a common trap is assuming the trigger automatically watches all subfolders, when in fact you must manually narrow the scope. If you ever face a Power Automate flow not triggering on a SharePoint folder, always check the trigger’s folder path first. Memory tip: “Root is mute for the subfolder route”—the trigger only listens where you point it.

⚠ Common exam trap

The trap here is that candidates mistakenly think the 'When a file is created' trigger automatically monitors all subfolders, when in fact it only monitors the exact folder path specified in the trigger configuration.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

The flow is configured to trigger on file creation in the root of the document library, not the 'Pending' folder

The most likely cause is that the flow trigger is configured to monitor the root of the SharePoint document library rather than the specific 'Pending' folder. Power Automate's 'When a file is created' trigger requires explicit folder path selection; if the trigger is set to the library root, it will not fire for files created in subfolders unless the trigger is configured with the folder path pointing to 'Pending'. This is a common misconfiguration when the trigger scope is not narrowed to the intended folder.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

✓
The flow is configured to trigger on file creation in the root of the document library, not the 'Pending' folder
Why this is correct
The trigger might not be scoped to the folder if the folder path is not correctly specified or if the trigger uses a different scope.
✗
The condition expression is incorrect, causing the flow to fail silently
Why it's wrong here
The condition is only evaluated after the trigger and approval; the flow does not trigger at all.
✗
The flow uses a 'When a file is created' trigger, but the file is being modified, not created
Why it's wrong here
The scenario describes file creation, so the trigger is appropriate.
✗
The flow requires a Power Automate per user plan
Why it's wrong here
This trigger is available with Office 365 licenses and does not require a per user plan.

Go deeper

1 more way this is tested on PL-900

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. You are reviewing a Power Automate flow definition. The flow should send an email when a new invoice file is added to a SharePoint folder. However, the flow is not triggering. What is the most likely cause?

medium

✓ A.The folder path '/documents/invoices' is incorrect or the flow lacks permissions.
B.The email action uses an incorrect dynamic expression.
C.The flow needs a 'Get file content' action before sending email.
D.The SharePoint trigger requires a 'When a file is created or modified' trigger instead.

Why A: The most likely cause is that the folder path '/documents/invoices' is incorrect or the flow lacks permissions. Power Automate triggers for SharePoint require exact folder paths and appropriate access rights to monitor file additions. If the path is misspelled, uses a relative path instead of a server-relative path, or the service account does not have read permissions on the folder, the trigger will not fire.

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This PL-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-900 exam.

Why Your Power Automate Flow Doesn't Trigger on a SharePoint Folder

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question

1 more way this is tested on PL-900