Share
Report
200Hello, I have a process that i am currently rewriting and consolidating into a single flow, but i am wondering if there is a reason why i shouldn't structure it this way. My current flow looks like this
- In my first flow, I import a table from excel into Lists, and then send a teams message to everyone who is present on that table that they have an item that needs to be reviewed.
- In my second flow, i get my sharepoint list to see if there are any records that are 7 days old and which havent been reviewed yet. If so, i send another teams message to each person askign them to complete thier review.
- In my third flow, i get my sharepoint list to see if there are any records that are 14 days old and which havent been reviewed, and if so, i send a message to the manager lettign them know that the review is outstanding so they can follow up with the person.
Because i dont know when the first step that creates the record will run, flows 2 and 3 run every morning so they can catch the 7 and 14 day windows.
I am in the process of expanding my 1st flow, so that the 2nd and 3rd steps happen in paralell branches after a 7 and 14 day delay. This means that my flow, will take 2 weeks to complete, instead of the few minutes that it takes for the first part to run. My thought is that this will be better, since i wont be running my other flows every morning. Also, it will be nice to have this process in a single flow, instead of having to scroll through all my flows to find one of the parts when i need to make updates.
Is there a reason why i shouldnt structure my flow this way?
All responses (
Answers (
