Planner due dates created by Power Automate often look wrong because the flow sends a timestamp in a different time zone than the team expects. A task meant for 9:00 AM can land late, early, or even on the previous day when the trigger sends UTC or a text date without a clear zone.
Fix the flow before editing tasks manually. If the task starts from an Outlook message, compare the upstream process with the Outlook-to-Planner task workflow so you know which connector supplies the original date.
Find the raw date value first
Open a recent run and inspect the trigger output or the action that supplies the due date. Copy the raw value before it reaches Planner. Many connectors display local time in the app while sending UTC to Power Automate.
- Capture the source value from the run history.
- Capture the value sent into the Planner due date field.
- Compare both values with the task shown in Planner.
- Note the expected local time zone for the team.
If the same offset appears every time, the flow needs a conversion. If only some tasks shift, look for date-only values, manually typed text, or tasks created near midnight.
Convert once and name the result clearly
Add a Convert time zone action before the Planner action. Set the source time zone from the trigger, the destination time zone used by the team, and a format the Planner connector accepts. Then map only the converted output into Planner.
Do not scatter date expressions across several actions. A single conversion step named something like Due date in team time zone is easier to audit and harder for the next editor to remove by mistake.
Test the boundary cases that usually fail
Run controlled tests in the morning, late in the day, and near a daylight saving change if your region uses daylight saving time. A flow can look perfect at noon and still shift dates when the converted value crosses midnight.
- Create one test task from a normal business-hour source date.
- Create one test task from a late-day source date.
- Compare the run output with the Planner task result.
- Correct only the production tasks created by the broken version of the flow.
If you later export tasks for review, consistent due dates are easier to inspect in Excel. The Planner-to-Excel export guide can help you audit whether the repaired flow is creating dates consistently.
Questions before you reuse the flow
Why does Planner show the previous or next day?
The converted timestamp may cross midnight in the team’s local time zone. Convert the source value before Planner receives it and test a late-day example.
Can I fix this only with date formatting?
No, not reliably. Formatting changes how the value looks. Time zone conversion changes the moment the value represents. Convert first, then format only if the connector requires it.
Should I store due dates as date-only values?
Use date-only values only when the workflow truly does not care about the hour. If reminders, handoffs, or reports depend on time, keep an explicit converted timestamp.
The useful repair is to make the flow honest about time: identify the source zone, convert once, map the converted value, and keep one known-good test case with the flow.