You’re offline. This is a read only version of the page.
76
Hi,
I have a SharePoint list with lots of columns (~60) and has ~ 10 different flows to trigger at different times depending what the value of my status column is currently.
All of these flows start with the trigger "When Item is Created or Modified" because I cannot see a more specific one.
The first action in each flow is to check that the status column has the value they are looking for, if not then it finishes -> if it is the right status may send an email to the manager then change the status to a new value[so the flow doesnt get stuck in a infinate loop] (which modifies the SharePoint item and all flows try to run again until the first check.)
It is taking almost 10 minutes before some flow runs.
I have a status saying "Sent for Review" and a flow that checks for this status and then depending on a "Review response" column decides to change status the column to "waiting for implementation" or "rejected".
In this scenario my Item stays at the status "Sent for review" when the "Review response" has already been changed to rejected for about 10 minutes before the flow runs and changes the status. Users are complaining that it is not clear where they item is in the process because it is not updated instantly and they cant instantly see in their list which ones they have responded to right away
Is this because all my flows try and run when the item is created and only one can be active at a time? Does each flow that is set to activate run sequentially? If so how long is the delay before the next flow is called and is there any way to run in parralel?
The flows only edit the item if their specific status matches so I know they arent trying to cause save conflicts.
HI @Zango
Your new approach is absolutely correct.
Each flow has a time to verify again if has 'new data' to trigger, and we cannot control this with accuracy.
The best way is use One flow as hub to call another flows, today with the possibility to change trigger will be easy to change from 'When a item was modified' to 'When a HTTP...'.
To maintain the data structure don't forget to persisty it using the 'use sample payload to generate schema' , you can get the body of one succeed execution and use as sample
Isn't flow fun?! You get to do things that the product should already be providing friendly abstractions for in the first place. YAY!!!!!
UPDATE:
After looking at how people solve the issue of having flows last longer than 30 days maybe HTTP requests could help me out.
I am now thinking I should have one SharePoint flow to activate "when Item is created or modified"
In this flow I should check the status field and create a HTTP Post request for each seperate step i want to take.
Then i should create numerous flows with the trigger "When a HTTP request is recieved" and i am thinking I should be able to structure my flows how i have before and possibly even ignore the check for the status because i am just waiting for the exact HTTP post request
#1
WarrenBelz
146,660
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,999
Most Valuable Professional
Share
Report
All responses (
Answers (
