I thought "We do not limit workflow runs"

This is what i got an email from bubble

"We are sending this email to let you know that your application has hit its maximum capacity usage for 14 minutes over the last 24 hours.

You can add more capacity to prevent your app from being rate-limited. You can do this in the Editor. You can also analyse your application’s capacity usage and control the threshold for these automated email notifications in the Logs Tab.

Don’t hesitate to reach out if you need help in scaling your application."

This whole server stuff needs more explanation, please anybody?

Capacity is a pretty confusing topic for most folks. There are several forum threads floating around about Capacity, some of those might help. It is not related to the number of workflow runs directly, but rather how much CPU usage is being spent on your app.

Capacity usage is only when i use server side workflows, or client based workflows is included?

And is any database action (like “Create new thing”) considered a “server-side” workflows?

And what does it mean when bubble says “We do not limit workflow runs”.

They used to have a limit of how many workflows could run per month. So, you might only be allowed 1000 workflow runs per month depending on what plan you had. This is no longer the case.

Database actions are definitely server-side.

So whats the point of unlimited workflows and hitting a capacity, and what does it mean hitting a capacity? does the workflow stop working, does it slow down, or what?

You can have workflows that are really cheap to run, and those that utilize a lot of CPU cycles. If you have really intense workflows, that eat up a lot of CPU cycles, you should either increase your capacity or try to refine the workflows.

It’s just like your computer at home. You can’t run 8 instances of an intense game without your computer slowing down to a crawl, it’s the same thing for servers. You can either close some instances or buy a better computer.

I think i’m starting to understand it, thanks

It’s confusing! In general, when I see I’m hitting capacity, I check these things:

  1. How many users were active at that time?
  2. What’s the workflow or action that’s causing the spike?
  3. Can I see why that workflow/action might be an issue?
  4. Buy capacity if I can’t optimize further
1 Like

the question is the capacity numbers, for example i received this email as a single user testing the app, with average heavy workflows, how will this app even be useful once it goes live to the masses?

is the capacity really that low?

im quite concerned

1 Like

I’d wager the workflows aren’t as efficient as they could be. If you’re seeing issues with one user, that’s where I’d start. Also, what type of plan are you on?


Ah, ok. So you don’t get any reserved server capacity, which (I think) means your capacity is shared with everybody else. I think you get reserved capacity at the next tier up.

1 Like

i have quite a few workflows which operates data actions on a list of things which as i understand from other threads that it might be CPU exhaustive.

Do you think upgrading to professional will be a significant help, and is it worth the money given i’m still in middle of developing the app for the next 3 months?

1 Like

If you don’t have users, I’d maybe hold off. When you add them, add some in waves and see what it does to your system.


Kudos, @andrewgassen, for being so clear and helpful in your answers.


So I’m on the professional plan with two extra units purchased and i received the same capacity email under the same scenario, just me testing things out. I have the same concerns. I tried to get clear explanation from bubble support but never did, only a if it continues to happen we’ll look further, or something like that.

If you share some screenshots of your complex workflows, the folks in the community it might be able to help figure out where the bottlenecks are.

This topic was automatically closed after 70 days. New replies are no longer allowed.