Flows not triggering/taking too long once they are triggered

[manan]

my flows, which usually take ~5 seconds to run, have been in the ‘running’ state for 10+mins.

there’s just a spinning logo in the ‘run details’ part, nothing else.

this was happening an hour ago, but now the flows are not even triggering. one of my flows uses a grist trigger, and the other one uses a webhook

is anyone else facing a similar issue?

[abuaboud]

The team is notified automatically, and it has now been resolved. Executions don’t get lost; they are just queued.

We will add more visibility for you, the user.