Share
ReportHey there,
I am trying to create a set of two flows: one doing the actual work, and the other one simply triggering the first flow at a rate of 30 flows per minute via HTTP.
I've been trying to make this work, but every time the executor flows start getting (for loss of a better description) "stuck" after about half an hour. A subset of the flows will get into this state which will fill up the max concurrency and grind the entire process to a hold.
The interesting thing is that there are no visible errors in this state, most look like this:
It seems to simply stop processing, most often directly in the trigger, but sometimes also within the scope somewhere.
Any clue what could cause this? Maybe a limit I'm not aware of since it seems to happen after around 30 minutes of 30 triggers per minute?
All responses (
Answers (
497
