Create tasks with label in planner on incoming mail

[ferpect]

Hi all,

I have created a flow that creates a ticket in planner when a mail is received. Based on keywords in the mailbody, different labels should be set.

This works so far. The tickets are created with different labels. But when I run a test with power automate, it spits out an error message when creating the "Label Funky" (framed in red in the screenshot above).

Here the error-message:

I have tried many things, changed the order of the conditions, recreated them, renamed them and so on, but I always get the same error.

ANYONE who has an idea?

[David_MA]

Can you show how the update task details action is configured since that is the action with the error?

[ferpect]

Hey David_MA,
sure, here is the error description:

[David_MA]

That doesn't show how you have the action configured. It shows the results of the run. However, based on this information, you are not passing the task ID to the action since it is showing null in your screen shot. You need to tell it the ID of task you want to update, which you can get from the create task action of the one you are trying to update.

[ferpect]

Thanks for the quick feedback. Unfortunately, I still don't quite understand what the error is or what I should do.

Here is the code of Create task with label "Funky"

Here is the code of Create task 2 with label "Copy"

And the code of "Update task details"

I don't see any difference between the two create task actions and therefore I don't know what to adjust.
Can you explain to me where exactly the error is and what I have to change?

[ferpect]

Hey,
sometimes you can't see the forest for the trees (German saying translated 1:1 - don't know if it's understandable). The solution was that I had to insert a separate task update in each condition.
Thanks for your questions, they have finally led me to the solution (even if I was very blind at first 😉 )

[David_MA]

I don't want to see the code, I want to see how you have the update task action configured. For example:

[ferpect · Accepted solution]

Ok, sure. Here it is

as described in my last comment, thanks to your questions and a look into the code, i have detected the error. now the flow looks like this and everything works as it should. thank you!

[David_MA]

I am glad you figured it out!