Demonstrate the capabilities of Power Automate →mediumMultiple Choice

Power Automate Trigger Required Property Error: Causes and Fixes

Exhibit

{
  "triggers": {
    "When_a_new_email_arrives": {
      "type": "ApiConnection",
      "inputs": {
        "host": {
          "connectionName": "shared_office365",
          "operationId": "OnNewEmail"
        },
        "parameters": {
          "folderPath": "Inbox",
          "importance": "High",
          "onlyWithAttachments": true
        }
      }
    }
  },
  "actions": {
    "Send_an_email": {
      "type": "ApiConnection",
      "inputs": {
        "host": {
          "connectionName": "shared_office365",
          "operationId": "SendEmail"
        },
        "parameters": {
          "to": "support@contoso.com",
          "subject": "High importance email received",
          "body": "Check your inbox for an important email."
        }
      }
    }
  }
}

Refer to the exhibit. A Power Automate flow definition is shown. The flow is supposed to trigger when a high-importance email with attachments arrives in the inbox, and then send a notification email to support. However, the flow does not trigger for emails that have attachments but are not marked as high importance. What is the most likely reason?

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 importance filter is set to 'High', so lower importance emails are ignored.

The trigger parameters include 'importance': 'High', so only emails with high importance trigger the flow. If the email has attachments but is not marked as high importance, the flow will not trigger. Option A is incorrect because the folder path being set to 'Inbox' does not affect the trigger; the trigger fires on new emails arriving in the inbox regardless of folder. Option B is incorrect because attachments are set to 'Yes', meaning attachments are required, but the flow still triggers only on high-importance emails; the issue is the importance filter, not attachments. Option D is incorrect because the trigger is set to 'When a new email arrives', which fires on new emails; the email being read does not prevent the trigger from firing on arrival.

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 folder path is set to 'Inbox' but the email was moved to a different folder.
Why it's wrong here
Folder path affects which mailbox folder is monitored, not the importance or attachment filters. Emails with attachments in the Inbox would still trigger if those conditions matched. This would be correct if the flow monitored a subfolder while messages arrived elsewhere, such as a rule-moved folder.
✗
The trigger requires attachments, so emails without attachments are ignored.
Why it's wrong here
The trigger's attachment condition is satisfied by these emails, so it cannot explain the failure; the stem's emails all have attachments. Attachment filtering is genuinely useful when you want to act only on mail carrying files, which is a valid design in other flows.
✓
The importance filter is set to 'High', so lower importance emails are ignored.
Why this is correct
The trigger's importance condition filters on 'High', so messages with Normal or Low importance never satisfy the trigger and the flow does not run. Attachment presence is irrelevant because the importance filter excludes those emails first.
✗
The trigger is set to 'When a new email arrives' but the email is already read.
Why it's wrong here
Read status is unrelated: the flow fails on unread high-importance mail lacking the importance flag, and the trigger fires on arrival regardless. The read/unread distinction matters only when a flow must process previously opened messages.

Go deeper

Power Automate Trigger Required Property Error: Causes and Fixes

Exhibit

Why each option matters

Option-by-option breakdown

Related to this question