Possible Bubble limitations / dead-ends?

Anytime! And yes, more capacity/higher plans increase the speed from what I’ve read in the forums from folks with Professional/Dedicated Plans. However, it’s still a debate as to HOW MUCH speed you get vs. lower capacity plans. Bubble has put forth a great effort in giving information to help us determine this, including the ability to add temporary capacity so you can test first without going to a higher plan… But from what I’ve seen, there still is quite a bit of confusion as to how much impact extra capacity really has… To boot, some folks just have poorly optimized sites.

As far as inherent limitations, there are a few.

#1: Crons - (Known in Bubble as Schedule Recurring Event). Crons are the ability to run code at a specified time outside of your application. I used it mainly for doing automated cleanup on databases (if items in database are older than 30 days, remove). In the programming world, we use crons ALOT… However, in Bubble, how often you can run crons is dependent on your plan. Dedicated (I believe $500/month+?) gets you daily crons. I have a Personal plan for my current app, so I can only run 1 monthly. You can use outside Sources, like NodeRed (which is what I do), however, doing that just adds more development time.

#2: APIs - First, they are rate limited to 1,000 requests/minute. Second, I believe there is a timeout… In my Wrike implementation, I attempted to pull 800 tasks and it failed every single time after about 15-20 seconds. I seem to recall something in the documentation about 4 minutes being the official timeout…? In Postman, it took around 2 seconds to load all of them. I think it took much longer in Bubble because I took the data from the API and attempted to put it into a Repeating Group (Bubble’s version of a “looped” table) immediately.

#3 - Database/Lists: @NigelG is the expert on all things Database in Bubble. Database record limit. <-- Link to his post about the record limit. Another great post on this is Limitations running workflows on a list <-- Look at @josh post from Oct 17.

Hopefully that helps!