Hey guys, so to follow up on this thread:
I took a look at @vincent56’s app, and found both a general issue and a specific one. Both issues are with Bubble, not with his app, so we’ll fix on our end. Expected ETA is in the next 1 - 2 weeks.
The general issue is with the capacity system as a whole: until an app is maxed out on capacity, Bubble will try to execute all requests as fast as possible. For small items of work, this is good – it means that as long as long as you have capacity, Bubble is as fast as possible. But for longer things, like doing an operation on a long list in an API workflow, Bubble might use up all your app’s capacity on that, instead of sharing that capacity with other things your app is trying to do.
So, the fix there is that we’re going to make Bubble smarter about how much of your app’s capacity can be spent on any one thing, and which things are more important. So if you have a background API workflow running, we’ll rate limit it so it never takes up too much of your capacity, leaving your capacity free to handle something more urgent, such as a user trying to load the page.
The specific problem – which is related – is with a workflow in vincent56’s app that deletes a list of things. It turns out that deleting a list of things is heavily parallelized right now, whereas most list operations we process things one at a time. What that means is that when we are deleting a list of things we end up doing a lot of work very quickly, so it can consume all an app’s capacity. (Deleting things is particularly work-intensive because we have to track down other items that reference them and delete the references … that’s the part that we are doing in parallel right now).
The fix for that is that we’re going to change the deletion action to be less parallelized, since again we don’t want to use all the app’s capacity on any one particular operation – better it runs a little slower in the background.