You’re offline. This is a read only version of the page.
143
Dear community,
we had a couple of failures recently, due to timeout. Flow took too long to respond.
Apparently offender is this scope part: it has two Compose steps, each run OK, pretty fast.
But the Scope itself took whole 2 min.
Why is that and what can be done about it, besides increasing the timeout?
Thank you,
Inna
Its ok if its a malformed value provided the flow did not actually take 2 minutes to complete the scope. To me this is a huge issue as you cannot accurately assess issues. I have a flow that sends 14 emails in 5 min. The flow continues to run for 12 min. There are no errors in the flow and the output is 100% what was expected. Once the flow reaches about 12 min it end and then the run execution says it was not 5 min. So I waited 12 min for it to complete even though it was actually done. Hence you cannot just dismiss the timing as malformed if it matches the actual time to run.
hi @in2217 scope is a separated space, like a group so sometimes the number of seconds are malformed. See your flow runs actually in 7s because the compose inside has 5 and 2 seconds. don't worry about the seconds of scope
#1
WarrenBelz
146,524
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
65,906
Most Valuable Professional
Share
Report
All responses (
Answers (
