Unanswered

Scope Intermittently Takes Hours to Run

(0) Share

Report

Posted on by BB-18031745-0

Hello,

I've been using this flow for several months with no problems.
Lately, for seemingly no reason, the flow which normally takes approximately 2 minutes to run will go on for hours.
When I check the run, it seems like a random scope will take hours to run when the runtime of the actions in the scope take nearly no time at all (see screenshot)

In this case it took 2 hours to run, in some situations it has taken 12 hours or more.
Has anyone else run into this before? Any likely reasons for this to occur?
This happens fairly rarely, but when it does it throws a wrench into things.

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (0)

David_MA 13,434 Super User 2025 Season 2 on at

Like (0)

Report
Copy link

Link copied!
You'll need to provide more information.

For example, what is the flow doing?

How is it triggered?

Is the same amount of data processed when it runs in minutes as when it takes hours?

If no, why do some runs process more data than other?

Are you using list rows/list items with a filter query, so it returns different amounts of items.

Was this reply helpful? Yes No
BB-18031745-0 47 on at

Like (0)

Report
Copy link

Link copied!
Hi David, here are the answers to your questions.

This flow grabs items from a list, checks the status of the items, and sends out emails where needed

It's a recurrence trigger every 45 minutes

Yes, in the example, the same amount of lists were checked and no emails were sent out. For the specific scope you see in the screenshot an array is filtered yielding an empty array, its combined with another array which was also empty in this instance, that array is fed into a select action which results in another empty array, the elements of that array are joined as a string and appended to a string variable, the array was empty, so this just does nothing in this situation

Yes, as described above.

This run was as simple as it could get and each action sums up to 0 seconds within that scope as you see in the screenshot, yet somehow the scope took 2 hours to run.

Was this reply helpful? Yes No