Trigger not receiving data – The trigger did not receive the expected data.

Power Automate triggers are responsible for starting flows when specific conditions are met. However, you may encounter the following issue:

“Trigger not receiving data – The trigger did not receive the expected data.”

This means the flow did not start because the expected data was not sent to the trigger, preventing it from executing properly.

---

2. Causes of “Trigger Not Receiving Data”

Several factors can cause this issue:

1. Incorrect Trigger Type – The wrong trigger type was used, and it is not receiving input from the intended source.
2. Missing or Incorrect Parameters – The trigger is expecting specific parameters, but they are missing or incorrectly formatted.
3. Data Source Issues – The connected data source (PowerApps, SharePoint, HTTP request, etc.) is not sending data properly.
4. Authentication and Permission Problems – The flow may not have the required permissions to access the data.
5. Network or Service Outages – Temporary Microsoft or external service outages can prevent data transmission.
6. Environment Mismatch – The flow and the source application (PowerApps, Dynamics 365, etc.) are in different environments.
7. API Throttling or Execution Limits – Power Automate has limits on trigger executions based on the plan and service constraints.
8. Incorrect JSON Format in HTTP Requests – If an HTTP request trigger is used, incorrect JSON structure can prevent data reception.
9. Trigger Condition Not Met – The data received does not match the trigger condition, so the flow does not start.
10. Trigger Is Disabled or Flow Turned Off – If the trigger or flow is disabled, it will not receive data.

---

3. Step-by-Step Troubleshooting Guide

Step 1: Check Flow Run History for Input Data

1. Open Power Automate (https://flow.microsoft.com).
2. Navigate to My Flows and select the affected flow.
3. Click Run History to view recent runs.
4. Open a failed run and check the Trigger Input section to see if any data was received.

Example of Expected Data in Run History:

{
  "UserID": "12345",
  "Status": "Active",
  "Priority": "High"
}

Example of Missing Data:

{}

Solution:

• If no data is present, verify that the source application (PowerApps, SharePoint, API, etc.) is actually sending the required data.

---

Step 2: Verify That the Correct Trigger Type Is Used

Different flows require specific triggers. Ensure you are using the appropriate one for your scenario:

Common Triggers and Their Use Cases:

Trigger Type	Use Case
PowerApps (V2)	When triggered by a PowerApps action
When an item is created or modified (SharePoint)	For SharePoint list updates
When an HTTP request is received	When external systems send data via HTTP
When a row is added/modified (Dataverse)	For Dataverse table updates
Recurrence	For scheduled flows

Solution:

• If the incorrect trigger type is used, replace it with the correct one and reconfigure the flow.

---

Step 3: Ensure Input Parameters Are Being Passed Correctly

If the trigger expects parameters, verify that they are correctly formatted and passed.

Example of a Correct PowerApps Flow Call:

Set(response, 'MyFlow'.Run("12345", "Active"))

Incorrect Example (Missing Parameters):

'MyFlow'.Run()

Solution:

• Ensure that all required parameters are passed in the correct order and format.

---

Step 4: Check If Data Source Is Sending Data Properly

If the flow is triggered by SharePoint, Dataverse, or an API, verify that the data source is correctly sending updates.

1. If using SharePoint, ensure that:
   • The correct list/library is selected.
   • The trigger is set to fire on the right event (Create or Modify).
   • The item being updated meets the trigger conditions.
2. If using an HTTP Request trigger, ensure the correct POST method and JSON format are used.

Correct HTTP Request JSON Format:

{
  "UserID": "12345",
  "Status": "Active"
}

Incorrect JSON Format:

{
  "UserID": 12345,  // ❌ Missing quotes around string values
  Status: "Active"  // ❌ Missing quotes around key
}

✔ Solution:

• Validate JSON structure using JSONLint before sending the request.

---

Step 5: Confirm That the Trigger Condition Is Correct

If your flow uses Trigger Conditions, ensure they are correct and met by the incoming data.

Example of a Correct Trigger Condition:

@equals(triggerBody()?['Status'], 'Active')

Incorrect Example (Field Name Incorrect):

@equals(triggerBody()?['status'], 'Active')  // ❌ 'status' should be 'Status'

Solution:

• Check the field names and values in Flow Run History to confirm that the condition matches the incoming data.

---

Step 6: Verify Permissions and Authentication

• If the flow is triggered by a SharePoint or Dataverse event, ensure that the flow owner has access to the data source.
• If the flow is triggered by PowerApps, confirm that the user running the app has permission to execute the flow.

Solution:

• Re-authenticate the connection in Power Automate by clicking Data > Connections > Edit Connection.

---

Step 7: Ensure That Power Automate and Data Source Are in the Same Environment

• If PowerApps is in Environment A but Power Automate is in Environment B, the trigger will not work.

Solution:

• Move the flow to the same environment as the data source.

---

Step 8: Check If the Flow Has Been Disabled

• Open Power Automate > My Flows.
• Ensure the flow status is “On”.
• If the flow was disabled due to API throttling, check Power Automate plan limits.

Solution:

• If the flow was disabled automatically, re-enable it and check for API limits.

---

Step 9: Test the Flow Manually

1. Open Power Automate > My Flows.
2. Click on the flow and select Test > Manually Trigger.
3. Provide test input data.
4. If the flow runs successfully, the issue lies with the source application not sending data.

Solution:

• If the flow works manually but not automatically, investigate whether the source system is correctly sending data.

---

4. Preventative Measures

To avoid “Trigger Not Receiving Data” issues in the future:

✔ Use PowerApps (V2) instead of PowerApps (V1).
✔ Ensure the correct trigger type is selected.
✔ Verify that all required input parameters are passed.
✔ Check Power Automate permissions and authentication.
✔ Monitor Flow Run History for missing data.
✔ Test the flow manually before full deployment.
✔ Confirm that Power Automate and the data source are in the same environment.
✔ Ensure proper JSON formatting when using HTTP triggers.