web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Planner 'Id' is 'null'...
Power Automate
Unanswered

Planner 'Id' is 'null' when updating planner task when the Condition 'No' branch is executed

(0) ShareShare
ReportReport
Posted on by 4

Hey everyone,

 

Hope someone can help me figure out this issue. I have a Conditional branch that puts an item in one Planner bucket or the other depending on a variable.

 

The 'Yes' and 'No' branch then converge to one common 'Update Task' where other details from the Forms are added in.

 

The issue I have is that when the 'No' branch is executed, the Planner 'Id' is 'null' when the 'Update task detail' step is executed.

When troubleshooting, I inserted an Email action within the 'No' condition and could confirm that the 'Id' is indeed generated.

 

 

No branch issue Flow.jpg No branch issue Flow - error.jpg

 

The 'Create task' is successful on the 'Yes' and 'No' branches.

The 'Update task detail' only fails on the 'No' branch due to the 'null' Planner Id. No such issue when the 'Yes' branch is executed.

 

Am I doing something wrong? 

Categories:
  • Mira Ghaly Profile Picture
    11,415 Moderator on at

    @naveensoman

    I believe you need to add the update task details under both branches and make sure you pass the planner Id from the relevant create task , it works for yes because you are passing the ID of the Create Task in the Yes Branch.

     

  • naveensoman Profile Picture
    4 on at

    Thanks Mira. I definitely plan to use that as a workaround, but why is the Id not being passed down the 'No' branch? Since the task is being created successfully and the 'Update' task is being run, the Id should have been passed down as well. Is this a bug?

     

    I definitely would have tried your approach if the 'No' branch terminated and the 'Update' task wasn't executed.

  • Mira Ghaly Profile Picture
    11,415 Moderator on at

    @naveensoman 

    Because Id comes from the Create Task of the previous step ..?

    SO you define a variable and set it to the Id and use the Id in the Update Task instead

  • naveensoman Profile Picture
    4 on at

    @Mira_Ghaly : The 'Create Task' is executed and an Id is generated on the 'No' branch. When the 'Update' task is run, the value of 'Id' is 'null' though for some reason. 

     

  • Mira Ghaly Profile Picture
    11,415 Moderator on at

    @naveensoman yes because it is trying to read from create take action in the yes branch 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
David_MA Profile Picture

David_MA 229 Super User 2026 Season 2

#2
11manish Profile Picture

11manish 223 Super User 2026 Season 2

#3
Valantis Profile Picture

Valantis 136 Super User 2026 Season 2

Last 30 days Overall leaderboard