Unanswered

Teams Presence and SharePoint List - Limits

(0) Share

Report

Posted on by lardo5150 Microsoft Employee

I have built a flow that grabs our engineer's teams status, and updates it in SPO List.

I am using a custom connector that authenticates to Azure, and then does microsoft graph to pull back the two status' of each engineer.

I do some checking then update each engineer in the SPO List.

I have around 100 engineers in the SPO List.

At first I had it set to run every minute.

This seems to work fine, but I came in one day and noticed towards the afternoon, I had a BUNCH of runs going, as they never finished, they were just running and running.

I thought maybe I hit some type of throttle.

So I increased the interval to 2 minutes.

I also added logic that if the flow takes longer than 2 minutes to run, to kill it (the flow only takes about 30 seconds).

I ran it like this for about two days, but noticed later in the afternoon it started to fail (it was taking longer than 2 minutes to complete, which made me assume I hit the throttle again.

I increased it to 3 minutes, it went longer but failed still.

I have it at 4 minutes now.

Question: Does anyone know what throttle I am hitting? is it graph? Azure? SPO?

I can't see in the flow where it is bombing cause it is an apply to each.

I was thinking of splitting up the list. Like grab the first half, get their info.

Then a second flow that grabs the other half and gets their info.

Any ideas on how to lower the interval but still not fail?

Categories:

General topics

I have the same question (0)

All responses (5)

Answers (0)

Hardesh15 7,087 Super User 2024 Season 1 on at

Like (0)

Report

@lardo5150 @Pls share your flow screens that will help us to see your flow design which causing to take longer run.

Please 'Thumbs Up' the posts that helped you and 'Accept as Solution' if my post answered your question.

@Hardesh /Gopenly.in

Was this reply helpful? Yes No
lardo5150 Microsoft Employee on at

Like (0)

Report

Here I have some other flows running, and I was getting conflict errors, so now I set it up to not run at top and half hour, as well as 8pm and after.

Here I grab all the engineers from the SPO list and cycle through them.
I have concurrency turned on set to 20, otherwise it will take up to and over 5 minutes to run.

Here, it failed because it was taking longer than 2 minutes, but I can't see where I was getting stuck

Was this reply helpful? Yes No
lardo5150 Microsoft Employee on at

Like (0)

Report

On this one, it just ran for longer than 2 minutes, but I can't tell why.

Was this reply helpful? Yes No
lardo5150 Microsoft Employee on at

Like (0)

Report

Any idea if you think I am hitting a throttle with SPO or the graph api?
I am wondering if turning on concurrency has anything to do with it?

What about splitting the get items up?

Was this reply helpful? Yes No
jerome18 24 on at

Like (0)

Report

Hi Lardo, recently i had to deal with a slow flow and found out an article from Tom Riha suggesting to replace 'Apply to each' with 'Select' or 'Filter array' to deal with this. You may have read it before but I share with you: https://tomriha.com/why-is-your-power-automate-flow-running-so-slow/
Hope this could help you solve this problem

Was this reply helpful? Yes No