@josh thank you for the detailed reply and analogy too. (Hopefully this will be useful to others also). My aim here was not to get bogged down on such a gnarly issue but more to understand the checks and balances in place so I can make informed decision. This method of charging is great and I have no issues on that count…
I appreciate that things are evolving when there is greater granularity on application usage this will help identify areas where the application may well be optimised… That will be a happy problem.
Thanks again
HI Josh, Your response clears up a few things for me thank you very much for the explanation.
First, it explains capacity and your analogy is a good one.
Second we were seeing this {“statusCode”:400,“message”:“Operation timed out – app too busy”} error and the page failed, not slow, spikey, etc. failed outright. This was happening for a couple of hours on Sunday and I have not seen it since.
Explaining that the bubble system was having issues on Sunday explains what the page was and what it meant. Without this explanation (not speaking for Bubbleboy but I think he felt the same) it made me think that my app would not run on Bubble.
So two issues here, capacity will always be something we need to manage. Our apps seem to be working fine, and the added dashboards will help us be better “developers” as we progress. The Sunday issue, failed pages, was an anomaly with Bubble and really coincidental with the capacity discussion. In fact its two different issues.
Thanks again.
Jeff
Hello everyone and @emmanuel,
I got an email this morning saying one of my Apps is maxed out as well! By 12 minutes over the 24 hours. 
But the only workflow is linked to its FB page! Could someone please show me where I mazed out the app? Thanks!
![42|690x353]
(/uploads/default/original/2X/5/57b7c5735d22cfad40e3a1b49c86db8735300261.jpg)
