web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Build Flow beyond 30 d...
Power Automate
Answered

Build Flow beyond 30 days with Reza Dorrani's tutorial using trigger"When an item is created or modified"

(0) ShareShare
ReportReport
Posted on by 20

Hi, I've made this flow, The problem is when it's run and there's some update item in SP list then the flow trigger more flow simultaneously

Kitaxay_2-1684461501727.png

 

Kitaxay_1-1684461452299.png

 

 

 

Categories:
I have the same question (0)
  • Kitaxay Profile Picture
    20 on at

    Hi, Any idea to avoid this one keep create new flow?

  • v-wenjuan-msft Profile Picture
    Microsoft Employee on at

    Hi @Kitaxay ,

     

    I check your snaps of your flow. Do you mean when you create a new item in the list, the flow will be triggered and update item in the same list. So that when the update happens, the flow will be triggered again. Thus, one creation leads to endless running of the flow.

     

    If so, advice is to limit the trigger only be fired when a new item got created in the list, which means when you do manually/automatically update work to the list items, the flow will not run. 

     

    @equals(triggerBody()?['Created'], triggerBody()?['Modified'])

     

    vwenjuanmsft_0-1684727260194.png

     

    Community Support Team _ Wenjuan Zou

    If this post helps, then please consider Accept it as the solution to help the other members find it.

     

  • Kitaxay Profile Picture
    20 on at

    Hi, Thanks for your suggestions, I've tested and let it timeout but it's not restart the flow.

    Column'StartWF' changed to YES

    Kitaxay_1-1684729089820.pngKitaxay_2-1684729121136.png

     

    @Anonymous(equals(triggerBody()?['StartWF'],'No'))

     

  • v-wenjuan-msft Profile Picture
    Microsoft Employee on at

    Hi @Kitaxay ,

     

    May I know what's the condition do you want to set to the trigger?

    Only when Column 'StartWF' modified to YES, rather than create a new item?

     

    Community Support Team _ Wenjuan Zou

    If this post helps, then please consider Accept it as the solution to help the other members find it.

  • Kitaxay Profile Picture
    20 on at

    Yes Sir, there will be both new items created and when Column 'StartWF' modified to YES, then start flow again from the beginning and catch the status for condition to switch case.

    Kitaxay_0-1684747000833.png

     

  • Kitaxay Profile Picture
    20 on at

    For more details:

    -When first case approved "StartWF" change to YES(mean start over again) 

    -Case"Status" changed to next approver case

    -then loop until finish all case

    Note: incase timeout 29days flow start from beginning with same status on current approver.

    Kitaxay_0-1684807289855.pngKitaxay_1-1684807342190.png

     

  • v-wenjuan-msft Profile Picture
    Microsoft Employee on at

    Hi @Kitaxay ,

     

    Thanks for your further explanation and hope I understand it correctly this time... So you would like to start the flow when you create a new item to the list and restart a new run when "update item" change "StartWF" to YES, am I right?

     

    If so, to avoid endless start over and to ensure the flow runs as expect, advice is to separate the two ways of trigger into two flows. One will be triggered when a new item is created and another will start when "StartWF" to YES.

     

    You can sustain the origin flow with trigger condition set to my previous suggestion.

    For the "modified" trigger, refer to below screenshot:

    vwenjuanmsft_0-1684813623010.png

     

    @not(equals(triggerBody()?['Created'], triggerBody()?['Modified']))
    
    sub(int(triggerOutputs()?['body/{VersionNumber}']),1)

     

    The settings will only start this flow when modification was made to items, then it will contrast current list with last version of list to check whether target column got changed. If yes, the flow continues. If not, like the modification happens to other columns, the flow will ends.

     

    Hope this helps~

     

    Community Support Team _ Wenjuan Zou

    If this post helps, then please consider Accept it as the solution to help the other members find it.

     

  • Kitaxay Profile Picture
    20 on at

    Hi V,

    I think separate flow is can solve. What if modified flow i want to make condition only run if column StartWF=Yes. 

    Stop run if StartWF=No.

    Kitaxay_1-1684816679907.png

     

    I have 3 approver step on the Status.

     

    Thanks

     

  • Kitaxay Profile Picture
    20 on at

    Hi V,
    In each switch case i have condition to start flow both Approved and timeout.

    This base on StartWF=Yes

    Kitaxay_2-1684817128254.png

     

  • v-wenjuan-msft Profile Picture
    Microsoft Employee on at

    Hi @Kitaxay ,

     

    Please refer to my yesterday's reply for solution. I have attached screenshots of steps to set a flow only run when StartWF column got modified. Next, you can put a condition there to tell whether StartWF=Yes.

     

    Community Support Team _ Wenjuan Zou

    If this post helps, then please consider Accept it as the solution to help the other members find it.

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Automate

#1
Michael E. Gernaey Profile Picture

Michael E. Gernaey 501 Super User 2025 Season 2

#2
Tomac Profile Picture

Tomac 323 Moderator

#3
abm abm Profile Picture

abm abm 237 Most Valuable Professional

Last 30 days Overall leaderboard