Task IDs keep changing

[davidntx]

I have been using Power Automate for about a year now, and I am in the middle of my biggest project yet.  I have years of programming background, so I understand the logic, variables, etc.  The problem I am having is with the Task IDs.

A user will complete a Microsoft form for a New Hire.  It is then saved through PA into a Sharepoint List.  From there I have my PA flow take the data and place it into tasks on the Planner.

Without getting into too much detail at this time, the flow checks "Condition" to check if it's a new hire or termination, then from there I use a "switch" to sort out the tasks by department.  When it works, it's a beautiful thing.  But too often I'll get "Not Found" and the task id's are out of whack.  Yes, I am creating several new tasks but from the research I've found, the task ID's should always stay the same.

I'm sure there are a lot more complex Power Automate flows working out there right now.  There is something about this that isn't clicking with me.  There are two possible "conditions" and 9 different "departments" in the switch.  I've gotten where I copy the long Task ID number from the "Create a Task" above it and paste that in to the "Update Task Details".  This just doesn't feel correct though, and will only work for one or two runs until that task ID in "create a task" changes.

Thanks for any help -

David

[v-jefferni]

Hi @davidntx ,

According to your screenshot, the flow stopped in the Switch control. But based on your description it was errored in the Update task details action which is above the Switch control and passed successfully. Could you please explain more on where and what the error is? 

Best regards,

[davidntx]

Yes, thanks you for taking an interest.

At the beginning of the flow, I set two variables - vReqType ("New Hire") and VarDept - which in the case is "HR".  The Condition matches for "New Hire", so it proceeds to the "Switch".  The Planner tasks created are different depending on which Department it is.

The logic itself is working.  I will get successful runs, then run it again and the very first "Update Task Details 1" were throw the error:  "Action 'Update_task_details 1' failed: The requested item is not found."  I correct the Task ID in Update Task Details 1", run the flow again, and it will error out for the NEXT task created. I fix that one, run it, and it throws the same error on the NEXT task created.  I fix that Task ID (which is the final task under "HR", after that my emails send successfully. and all is good.  

The next time I run the flow it starts over at the top, saying "Update task details" failed: The requested item is not found."  Then I start updating the Task IDs again by copying the task IDs from the first "create a task", and adding it to the first "Update Task Details", and so on til I get to the end again.

Like I said before, I know this is not a Power Automate issue, but a user error simply not understanding where that "Task ID" comes from.  I see videos of users simply selecting the dynamic field "Id" for each "Update Task Detail" assuming it will pull the task ID from the previous "Create a Task".  That simply doesn't work in my flow setup.

(FYI - I couldn't add the 4th attachment, which was a shot of the "Update Task Details" showing that the Task ID has changed again:  "sSnS5qPNVUeJljUJtwZPeWUAG89o")

Thanks for your guidance!

David

[v-jefferni]

Hi @davidntx ,

Could you please add a screenshot of the flow in EDIT screen and classic mode? I'd like to see the input in the 'Update task details' action.

Best regards,

[davidntx]

I hope this what you are asking to see...

Thanks,

David

[v-jefferni]

Hi @davidntx ,

Could you please explain why you are using fixed task IDs instead of dynamic contents from the previous Create a task action? I cannot understand the logic.

Best regards,

[davidntx]

Yeah, thanks for noticing that.  I mentioned before that this started because of the "object unknown" errors I was getting using the Dynamic "Task ID".  

Thank you for taking the time to look at my flow.  I think I'm just going to start from scratch.