Been logging unhandled errors on the frontend, and it seems users have been getting this error on a daily basis:
Unhandled Error: Workflows could not run because too many events triggered at the same time.
Any idea what’s this about? Thanks.
1 Like
Been getting this today as well. Has happened before. Have emailed support. Tested for workflow errors by removing the only slightly “heavy” workflow step, but still the same. There doesn’t appear to be anything huge happening in server logs, although the app does have 100+ users active at any one time.
1 Like
Yo, got this too on a previously working page!
Very strange: it works with the debugger ON, but if it’s not there, then it fails to load and I get that error message.
Error message has no data.
Does your page have graphs or tables? Mine does, but not clear if that’s causing the error.
Do you have multiple workflows being triggered by the same action?
Like a button with multiple events associated with it?
Hey, I don’t. It’s actually a tab button that just changes the page’s state to show or hide an element.
I do, but each workflow has conditions that are mutually exclusive of each other, so at most 1 workflow may run upon a trigger (e.g. button click).
Do you have multiple workflows being triggered by the same action?
Like a button with multiple events associated with it?
Is there any known issue with such workflows? I vaguely remember this being a potential problem a few months back, but can’t recall what it was.
I emailed Bubble Support and here’s their reply:
This error message is from a recent update we made that surfaces a more useful error as you see:
Workflows could not run because too many events triggered at the same timeThis error usually arises in the event of timeouts when your app is overloaded, replacing a much more generic message: autorun run_once timeout.
Timeouts precipitating this error can be caused by several factors, and commonly result from circular references in the logic of a given page. You may want to begin by checking your App’s server logs and attempting to identify if there are any clear indications of what may be causing this issue!
From the workload usage metries, it doesn’t look like my app was overloaded though…
2 Likes
No, my page doesn’t have graphs or tables. But it is a kind of heavy with many steps, nested workflows, and API calls.
Are you able to isolate or replicate the issue? My problem is that I can’t replicate it myself - only a few users encounter it sporadically.
Are you still with the old pricing? Or with the new one ?
I have a button that creates an account for someone else but it only works sometimes today - very weird. I did get this email from Bubble:
‘You’re getting this email because your app xxxx has used 50% of its available Things in its database. Apps on the Free plan that hit the limit of 200 database Things will no longer save any new Things to their databases.’
But if i’ve only reached 50% that shouldn’t affect it right?
200 ‘things’ may not be enough for me to test my app which is a shame because I am nearly converted to Bubble. My app is fairly complex with a number of related db’s - these necessitate having a reasonable number of record (things) in them.
I’ve tested and tested the Button and rebuilt the workflow from scratch - no errors but it just won’t start the workflow even in test mode.
Many thanks
I have not been able to isolate the issue. I’ll be picking apart the entire view and testing one thing at a time.
I’m on the new plan, too.
Also, what’s weird is that this doesn’t happen when debug mode is on.
I’m on the old plan. I think I’ll try to analyze the whole workflow again.
My users are reporting the same, on an app that’s worked fine for 9+ months. Log shows - Workflow error - Operation timed out – app too busy
1 Like
Hmmm, this might be due to some update on Bubble’s side.
I have had the same error for a few days. I have checked all the workflows as I have a small application, but I have noticed that this error also occurs when I leave the applications without clicking for some time. In my opinion, it is impossible to isolate this error because it also appears without performing any action. And I’m on a paid new plan
In my application I have found what triggers this error. For some unknown reason when clicking on a group to show a popup this error occurs. I have changed to Fontawsome element from which to click and it is ok but in my opinion it is a bubble error.
1 Like
Thanks for the insight 
Quick questions - do you have any condition on the workflow (that’s being triggered by clicking of the group)? Are there multiple workflows for clicking on that one group element?
No. Even I tried to show empty popup and I had the same error.
1 Like
Same problem here. Just 1 event associated with the button.