Forum Discussion
Planner Task Due Dates
I've been using planner for a few years at work amongst the team. We are each assigned to tasks with information and due dates. As of recently, if a task is due today (let's say September 18th), it will be in the "Past Due" bucket whereas it used to be in the "Today" bucket - this is when filtering by Due Date.
Any thoughts? Thanks!
3 Replies
- jwenzCHUBBCopper Contributor
Here's an image of this scenario for better context. With today being 09/21, the date should not be highlighted in red. This highlight equates to it being past due which is not correct.
- KellijoyriveraTin Contributor
How are these tasks being created? Are they being entered directly into Planner or created through Power Automate?
We've run into this exact issue with tasks created through Power Automate, and in our case, the culprit was time zones and the underlying due time.
Here's the frustrating part: Planner stores a date AND time for every task's due date, even when the interface only displays the date. So a task could show as "Due Today," but if the actual time attached to that date is 7:00 AM, Planner may mark it late at 8:00 AM, even though it's still the same day!
When creating tasks through Power Automate, we've had to explicitly set the due time (typically 11:59 PM) in our local time zone and then convert it to UTC before sending it to Planner. Otherwise, the time attached to the task can cause it to appear overdue much earlier than intended.
What makes this especially infuriating is that, depending on your version of Planner, you may not even be able to see that underlying time to figure out why the task is late.
I'd start by checking how the tasks were created and, if automation is involved, what date/time value is actually being passed to Planner. That hidden timestamp could very well be your problem!
- jwenzCHUBBCopper Contributor
Thank you! This is likely the culprit for sure. The tasks are created through Power Automate with the trigger being new row add in SharePoint. Will investigate.