Possible to build a flow with a chain of tasks - each created after the previous task has been completed?

Question

Hello everyone,

I've set up a flow that creates a new Task when a task with a specific Subject line has been completed. This then creates two new Tasks that are due in a couple of Days (Create Day 3 Call and Create Day 3 Send Email). I then want to check both these Day 3 Tasks status has been Completed using a Decision element (Day 3 Decision). If both are completed, a new Task is created. However it's at this stage that my flow doesn't work. The Day 5 Send Email Task isn't created.

I want to be able to set up this flow so that it creates up to 7 new tasks. Each one to be created when the previous 1 (or 2) have been completed.

This is an example of I've set up for the Get Records elements:

Get Records Element.png

This is my first decision element:

decision task flow.png

Is this possible to set up? Or should I create a new flow for each new Task I want to create?

I also get this error message against my Get Record elements: "Get_Email_Day_3_Task (Get Records) - The “Get_Email_Day_3_Task” Get Records element in this flow can cause performance issues. At run time, the flow starts an interview for each record specified in the Start element and stores each task in the $Record global variable. Check whether the “Get_Email_Day_3_Task” element is still necessary, or add a filter so that the element accesses only the task in the $Record global variable."

I'm not sure what to do here as if I use the $Record I can't access the Status for the two Day 3 Tasks.

Thanks for your help Trailblazers!

#flow

Michael Brown · Accepted Answer

Hmm, I think you might need a decision element up front with 4 outcomes. Ideally, the flow would then only trigger one of these outcomes.

Outcome 1: Task is completed with Specific Subject
1. If this outcome is met, create the Day 3 Tasks
Outcome 2: Task is completed, and it is Day 3 Call Task
1. If this outcome is met, we would then query for the Day 3 Email Task on the same parent record and determine if that is also completed. If so, you could create the Day 5 Email
Outcome 3: Task is completed and it's a Day 3 Email Task
1. If this outcome is met, we would then query for the Day 3 Call Task on the same parent record and determine if that is also completed. If so, you could create the Day 5 Email
Outcome 4: Task is completed and it's a Day 5 Email Task
1. Create the Day 7 Task

I hope that makes sense, but let me know if you need a visual.

Dan Brixey · Answer

Thank you both! Mikey I went with your suggestion just so I could get more Flow practice in. Here's what I built in the end. The Trigger checks if the task is Completed and the Subject contains "BDR Day". Then the Decision outcomes check if the task subject says "BDR Day 3", "BDR Day 5", etc. etc.    I also set RecordPrior.Status not equal to Completed in the Decision outcomes - that way if someone clicks Complete again, a duplicate Task isn't created.  There's a few potential problems, such as if someone deletes a task rather than completes it. But I'll see if that becomes a common problem and look to a solution for that after this has been tested by the team for a while.    Thanks both for your help, appreciate it.

Possible to build a flow with a chain of tasks - each created after the previous task has been completed?

Flow

Verwandte Lerninhalte

Weitere Hilfe