Concurrent Flow Runs

If the limit of concurrent flows are reached, do the rest get put in a queue, or does it fail? If it does get put in a queue, is there a limit to how many can be added or how long it will be there?

Hey @SimonSays! If you’re reporting an issue with a flow or an error in a run, please include the run link and make sure it’s shareable so we can take a look.

  1. Find your run link on the history page. Format: https://www.gumloop.com/pipeline?run_id={{your_run_id}}&workbook_id={{workbook_id}}

  2. Make it shareable by clicking “Share” → ‘Anyone with the link can view’ in the top-left corner of the flow screen.
    GIF guide

  3. Provide details about the issue—more context helps us troubleshoot faster.

You can find your run history here: https://www.gumloop.com/history

Looping @rahul-gumloop here ^

It just fails – so does not get put in a queue.

So any ideas on how to get around that?

There’s unfortunately no way to get around it. It must be managed on the client side – so if you are running automations from the UI, you’ll have to wait until your other automations complete.

If you are running it via webhook, you’ll have to handle the 429 and retries on your side.

This topic was automatically closed 60 minutes after the last reply. New replies are no longer allowed.