How to Fix Power Automate addDays and Planner Due Date Errors
Question details
The user needs to prevent Power Automate from incorrectly setting a Planner task's due date to its start date when the input due-date value is null or invalid.

- Product
- Power Automate
- Device & OS
- not provided
- Scenario
- Creating or updating a Planner task using Power Automate flows that involve dynamic date calculations.
- Observed behavior
- The due date defaults to the start date or today's date because the provided due date field evaluates to null, empty, or an invalid parameter during the addDays or coalesce expression.
Review your most recent failed flow run outputs to identify exactly which date fields are returning null or empty values before they reach the Planner action.
Validate Date Fields Using Conditions Before Task Creation
Stop the flow or handle empty values gracefully before passing null data into the Planner action.
By verifying that your start and due dates actually contain data before creating the task, you prevent the system from substituting unintended fallback values.
Edit your Power Automate flow and locate the step immediately before the 'Create a task' (Planner) action.
Insert a 'Condition' action. Set the left operand to your due-date dynamic content, select 'is not equal to', and leave the right side blank (or use the empty() expression).
Move your 'Create a task' Planner action into the 'If yes' branch so it only executes when a valid date is confirmed.
Inside the Planner action, apply your addDays() expression directly to the validated due-date field without relying on a fallback.
Modify the Coalesce Expression to Avoid utcNow()
Prevent Power Automate from automatically inserting today's date when the intended due date is missing.
Seamlessly Manage Project Data with WPS Office
While Power Automate handles automation across Microsoft services, you can easily manage, track, and analyze your exported Planner task dates and project schedules using WPS Office. It is a lightweight, completely free alternative that seamlessly handles all your document and spreadsheet needs.
- 1. Download WPS Office: Install WPS Office Free from the official website to your device.
- 2. Export Planner Tasks: Export your Microsoft Planner task list to an Excel (.xlsx) file.
- 3. Analyze Dates in WPS Spreadsheet: Open the exported file in WPS Spreadsheet to filter and analyze start and due dates without formatting issues.

Frequently Asked Questions
Why does my Planner task due date show as today's date instead of the future date?
This usually happens when the due-date parameter passed to Power Automate evaluates to null, and a function like coalesce() automatically falls back to utcNow(), defaulting the task to today.
How do I test for empty date values in Power Automate?
You can use the empty() expression inside a Condition control. For example, empty(triggerBody()?['DueDate']) evaluates to true if the field has no value, allowing you to route the flow appropriately.
What causes the 'invalid parameter' error in the addDays expression?
The addDays function requires a valid timestamp string as its first parameter. If the dynamic content passed into it is null or formatted incorrectly, the function will fail and return an invalid parameter error.
Can I create a Planner task without specifying a due date?
Yes, the due date is generally optional in Planner. If your flow logic allows it, you can leave the due date field blank in the 'Create a task' action when a specific date is not provided.




