I have an app that for the first time is showing an error “Operation timed out – app too busy” and I need some help figuring out how understand what the issue is, identify it, and solve it. This is the first time I’ve seen this issue so unclear how to handle it. I’m assuming it has something to do with the number of workflows being run.
Here’s the situation
The app that’s now timing out has been running for 5 months without any major adjustments or increases in uses so it seems strange.
Some workflow with “heavy” action(s) sent your app into max capacity, which would explain why your app timed out. Further down the page you can view capacity consumption. I generated a chart for the same time frame (7 am Eastern to 6 hrs later).
You can drill down on each piece of the chart to get more specific, and eventually you’ll be taken to the exact element, action, workflow event, etc. responsible for it.
From what I can see, you might need to re-work some of the logic to make it more efficient. I’m seeing a ton of “Search for” expressions in a single “Send Email” action that might be creating a bottleneck, exceeding capacity, and ultimately timing out.
Thanks for walking me through how to understand where the problem is. This makes sense. A few more questions that come to mind
Any idea why this would just be happening now? Nothing has changed about the use of the app in 5 months.
How do you define “efficient” in this case? Is it the number of workflows? Database queries? Any action that needs to get done?
Based on what you saw from the app, how would you make it more efficient? Since I don’t know the definition of efficient yet, I can’t think through how to make it more efficient.
Lastly, any insight into why this would be an issue now? Has something changed within bubble? The error does not replicate on my computer/browser but it does with my customers browers/computer. Also, the number of workflows run in November is lower then other months…
I noticed that too. It’s like API workflows make a slower response now. I’m still investigating. I tried with 10 credits (units), and everything’s was fine. Maybe Bubble can confirm if they have reduced the number of APIs workflows done simultaneously on their personal plan? Many others also observed. @eve ? @emmanuel ?
Thanks for exploring John. If you find anything, please let me know.
Also, what are “credits”? Are you saying that I can buy extra capacity (until I make the app more efficient) so it won’t time out? If yes, how do I do that? I tried to search around the bubble website and app and didn’t find a place to buy credits.
We’ve seen a few reports of API workflows taking up more capacity than they were previously, so that might be part of the issue here. I’m not able to accurately assess this without our team having a chance to investigate, so I’ve already requested that @topherwilliams file a bug report with our team and will make sure that gets addressed ASAP.
A little update on this thread. This situation is getting a little more confusing and frustrating. It’s clear that there is a problem somewhere, but no one can identify where it is.
I reported a bug to bubble, they cannot replicate, it still happens for me, so feels like a standstill.
Before all of this I made a copy of the original app, so I decided to make upgrades to that app, as it didn’t freeze.
To make the app faster and user fewer server queries, I started using “Current User’s Current Call” on all adjustments of a “Call”, instead of using “Do Search For…” database searches to create/edits items in the database, in this case it’s “Calls”
Example here:
I got the new app up and running yesterday and it worked fine. I purchased a “Professional Plan” for added server capacity to try to make sure it wouldn’t freeze.
What causes an operation timed out – app too busy?
It’s occurring to me that the navigation of workflows and states might be the issue and that it could create an infinite loop, which would create a timeout. This is just a logical observation, I don’t know the code that makes this.
Is there a way to make a chain of states so that the 1 triggers the next?
For example, I want to use states, but I want
1) email to be sent + triggers the right calendar request to be sent
2) calendar request to be sent
3) navigation to go to a new page
Update for everyone. I’ve changed nothing in the app and it works perfectly now.
My gut is telling me that there was a server side and/or bubble issue that was fixed. To me, nothing else can explain to me why magically my app stopped working, then magically started working again. If anyone else has a pet theory, or if this has happened to you, I’d love to hear it