How to Fix Power Automate Filter Array and HTML Table Errors for Email Alerts
Question details
The user needs to fix a Power Automate workflow that filters overdue activities, sends an HTML email alert, and updates the row, but encounters errors passing the Filter array output to the Create HTML table action.

- Product
- Microsoft Power Automate
- Device & OS
- not provided
- Scenario
- Building a workflow to send email alerts for overdue tasks by filtering rows where the status is 'NO' and the due date is today or overdue.
- Observed behavior
- The 'Create HTML table' action fails when using outputs('Filter_array')['body/value'] because the output contains 'body' instead of 'body/value'. This issue often occurs when switching between the classic and new Power Automate designers.
Before troubleshooting, run a test of your workflow and check the 'Run history'. This allows you to inspect the exact JSON output structure of your Filter array action before passing it to the HTML table.
Correct the Filter Array Output Reference in Create HTML Table
Resolve the error by matching your expression to the actual JSON structure returned by the Filter array action.
Depending on the version of the Power Automate designer you are using (Classic vs. New), the output of a Filter array action may be stored directly in the `body` or nested inside `body/value`. Referencing the wrong path will cause the Create HTML table action to fail.
Navigate to 'My flows', select your workflow, and open the most recent failed run from the '28-day run history'. Click on the 'Filter array' action to expand it and review the raw outputs.
Check if the filtered data array is located inside a property named 'value' or if it is the direct 'body' array itself. If you only see 'body' without a nested 'value', your expression needs to be adjusted.
Open your flow in Edit mode. In the 'Create HTML table' action, change the 'From' field. If your output did not contain 'body/value', use the expression `body('Filter_array')` instead of `outputs('Filter_array')['body/value']`.
Save the changes and click 'Test' in the top right corner. Select 'Manually' or use a previous trigger to verify that the HTML table generates successfully and the email alert is sent.

Manage Your Activity Trackers and Spreadsheets Seamlessly with WPS Office
While Power Automate is excellent for automating alerts, the underlying task trackers and data lists are usually managed in spreadsheets. WPS Office provides a free, lightweight, and highly compatible spreadsheet tool to manage your data, making it easier to track due dates and statuses without complex setups.
- 1. Download and Install WPS Office: Get WPS Office for free from the official website and install it on your device.
- 2. Open Your Task Tracker: Launch WPS Spreadsheet and open your existing .xlsx activity trackers natively.
- 3. Use Built-in Filters: Easily apply date filters and conditional formatting to visually highlight overdue activities directly within the spreadsheet.

Frequently Asked Questions
Why does my Power Automate flow fail at the Create HTML table step?
This usually happens because the input array is incorrectly referenced. Check your flow's run history to see if the Filter array output requires you to use body('Filter_array') instead of outputs('Filter_array')['body/value'].
How do I filter overdue dates in a Power Automate flow?
Use a 'Filter array' action and set the condition to compare your Due Date column against the current date. Use the expression formatDateTime(utcNow(), 'yyyy-MM-dd') and set the operator to 'is less than' to capture overdue items.
Why does the new Power Automate designer change my expressions automatically?
The new designer attempts to validate and format expressions automatically based on its schema. If it detects a mismatch, it may append or strip the '/value' path. Switching temporarily to the classic designer can help bypass this behavior while building complex arrays.




