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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Recurrence trigger cha...
Power Automate
Unanswered

Recurrence trigger changes flow duration from minutes to hours/days?

(0) ShareShare
ReportReport
Posted on by 2,567 Super User 2026 Season 1
Hi everybody,
 
we are currently implementing several flows which started as instant flows later to be changed to a scheduled one.
Changing the trigger is usually quite easy, not since a few days. When nothing is changed but the trigger from manual to scheduled and the flow is run either as a test or via the start button, actions are taking hours longer.
Nothing at all changes just the trigger.
Using a scheduled flow to start the normally scheduled flow as child flow also works fine (pic.2)
Anybody an idea?

 

Categories:
I have the same question (0)
  • Ellis Karim Profile Picture
    12,163 Super User 2026 Season 1 on at
     
    It's hard to offer any advice without seeing the flow.
     
    Start by turning off concurrency - if you have enabled that in the Apply to Each loop (For each Projectmappe - concurrent) and test the flow. Also, variables should not be used inside loops when you have concurrency enabled.
     
    Expand the "For each Projectmappe - single runs" and see which action inside the loop is taking so long.
     
     
     
     
     
    Ellis Karim
    Ellis Karim
    elliskarim.com  |  LinkedIn  |  Bluesky
    If this solved your issue, please mark it as ✅ Accepted Answer. If it helped, feel free to give it a 🩷 Like!
  • Lucas001 Profile Picture
    2,567 Super User 2026 Season 1 on at
     
    the concurrency has not been the issue here and variables neither.
    The workaround for now has been to use a parent flow and the one mentioned as a child flow.
    The parent flow is running scheduled which basically does entirely the same as intended, but solves the issue that the trigger somehow changes the flows behaviour. It literally a flow having a scheduled trigger running the child flow.
     
    This ticket unfortunately will stay open as the issue cannot really be reproduced for now and microsoft had no solution.
    Thanks for your answer anyways.

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

Season of Sharing Community Challenge Launch!

Jump in, show your community spirit, and win prizes!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the May Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Valantis Profile Picture

Valantis 377

#2
11manish Profile Picture

11manish 279

#3
David_MA Profile Picture

David_MA 234 Super User 2026 Season 1

Last 30 days Overall leaderboard