Unhandled Error: Workflows could not run because too many events triggered at the same time

[kossiorek1]

Please anyone can help with this ? I have just add new button without workflow and when I click I have this error again.

[jakub.jk.kaspar]

I am also having the same problem. Tried to re-do the workflow in many ways suggested but still it occurs. Is there already any solution that worked for any of you? I’ve just also reported this as a bug to Bubble.

[felipe.ns3]

Any reply from the support? Who managed to fix that?
The button here used to work in the past.

[lindsay_knowcode]

Also why with “unlimited capacity” with the new plans why do I see this throttling on capacity?

I’ll ask support.

[lindsay_knowcode]

Response from support … sadly it doesn’t really help me as I’m not processing a list of things or especially synchronous events - I just have a very busy app at times. But I love the advice to “think holistically” - that’s hilarious.

Thank you for following up. Apps do still have capacity limits and will be throttled if too much is happening at one time, as described in this manual entry instead of making changes to a list of things, for example, which allows you to set a time interval between each workflow execution.

[jared.gibb]

So…. Back to recursive workflows.??

Didn’t @josh say something about being able to run workflows on an Fton of records at bubbleCon?

[jared.gibb]

But hey there’s this

[Feature Enhancement] Improved Scalability of Schedule API Workflow on a List

Update: Please see my most recent post in the comments, which addresses frequently asked questions. Hi everyone, We’re excited to share that we’ve released an enhancement to Schedule API Workflow on a list. Previously, this action was only capable of scheduling a few thousand workflows before timing out. Now, users can reliably schedule and execute workflows on lists of tens of thousands of things! This ~10x improvement in scalability makes Schedule API Workflow on a list the best way to ac…

[lindsay_knowcode]

ha! not what I’ve observed.

[NigelG]

@lindsay_knowcode

But I love the advice to “think holistically” - that’s hilarious.

I think “holistically f***, what just happened” a lot of the time

@lindsay_knowcode

ha! not what I’ve observed.

Not seeing it either, sadly. My guess is that there a number of these soft limits at play, and it does depend on which one you are bumping up against.

[jared.gibb]

Would love to explore inside that blackbox we call bubble and understand actual capacities

I think if we didn’t have a dedicated instance our apps would shit all over themselves every day. Particularly our data curation internal app.

[marcov1120]

In my account, the issue was related to the script i was running in the header for my cookies policy. It slowed everything down. After i removed, it all started working normally.

[kossiorek1]

Today I solved the problem. The error was caused by a workflow in a reusable element. The element occurred several times on the page and had a workflow „when the page loaded” and interestingly it was disabled but causing the error. When I removed it the error disappeared. Probably in the workflow it wanted to load several times when the page was launched and that’s why it was causing the error. Check if you have this kind of workflow in your application on a reusable element that is shown more than once on the page.