Answered

Your flow is running too many actions

(0) Share

Report

Posted on by LarsHoubenDEV

I received an email that my flown is undergoing too many actions.
I am quite new and do not understand why.
The scenario I want to achieve is that my Name field in SharePoint is automatically updated using the Metadata entered.

I don't understand why the flow restarts every 2 minutes

Thanks in advance for the explanation and solution that you have for me

Categories:

Building flows

I have the same question (0)

All responses (5)

Answers (1)

Sort by

eetuRobo 4,583 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Your flow might be in an infinite loop. Are you sending the HTTP request to the same folder that it triggers?
If so
Flow triggers when file is created/modified
Flow modifies the file
That modification triggers the flow again
repeats

Was this reply helpful? Yes No
LarsHoubenDEV 11 on at

Like
a
(0)

Report
Copy link

Link copied!

Okay, that sounds very logical, so because of the HTTP Request it modified the file again.
So what is the solution to stop it from running after the HTTP Request?

Was this reply helpful? Yes No
eetuRobo 4,583 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Would your flow work if you changed it to "When a file is created" -action
So it would not trigger if its modified.
Or does the flow need to trigger when a file is modified?

Was this reply helpful? Yes No
LarsHoubenDEV 11 on at

Like
a
(0)

Report
Copy link

Link copied!

Eigatively also Modified, if they don't fill in the Metadata directly or they bulk load files, the name is never going to be correct.
Maybe the solution, is to use a condition.
If Modified not by Service account, do the http request

Was this reply helpful? Yes No
Verified answer

eetuRobo 4,583 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
Yes so if the flow cant use when created but also needs to include when modified then best way would probably be as you suggested to check who modified the file. You could do as you suggested condition that checks who modified it and as long as its someone else than the automation account then run the flow. Otherwise terminate the flow. That would start the flow twice every time so once more than needed.

The best way would probably be to add Trigger Condition so that your flow start every time to just terminate itself after your flow has modified the file.
So Add trigger condition under actions settings:

Then put something like this: in the condition:
@not(equals(triggerBody()?['Editor']?['Email'], 'automations@Email.com'))

https://powerusers.microsoft.com/t5/Building-Flows/Trigger-condition-When-a-file-is-created-or-modified-properties/td-p/503756

Was this reply helpful? Yes No