Modified Trigger - Creates Tasks in Specific Buckets already created - Duplicating Task in Bucket

[DL-HIA]

Process requires a user to fill out a new List item.

Part of the new item are 5 separates Tasks or "Action Items".

The user may not want to assign those at the time of creation, they may meet and then assign those Action Items (Tasks) to personnel.

I have a flow created already for Creation of the list item that creates a unique named Bucket in a specific Planner and also creates any Action Items (Tasks) if assigned at Creation.

Now created a flow for Modified item, so when they come back and decide to assign the other Action Items (Tasks), those cna be created in the properly selected bucket name.

The flow creates the first Action Item (A1) fine, when I go to add the next part for creation of the second Action Item (A2) it creates not only creates A2 but also re-creates A1 that was in that Bucket.

I would continue with the other Action Items, but I am sure they would just recreate the tasks before them in the bucket. A3 would recreate A2 and A1.

A4 creation would recreate A3, A2, and A1, etc.

How do I stop the recreation of any Task prior to the one being created in the proper bucket. Flow Pics below.

 

 

 

 

 

[Pstork1]

After you filter the buckets to get the bucket you want to add tasks to you need to list the tasks that are in that bucket. Then inside the apply to each you need to add a condition to check whether there is an existing Task that has the same Title as the Action Item you are about to add.  If it does then don't add another.  If it doesn't then do the create Task.

[DL-HIA]

But it is not recreating the Task/Action Item I am trying to create, A2; it is recreating the one before it that would have a totally different Name/Title A1 and was closed already in the bucket.

From reading what you have stated it would still create the A1 because it does not have the same title.

[Pstork1]

If not the title, then something else.  You need to be able to identify that A1 exists when creating A2 so you don't recreate it.  The way your flow is written now it will create a new all the tasks every time the item is modified.  You only want it to create tasks when new entries have been added to the item.