I consider myself still new to backend workflows, so I’m still not sure how certain aspects work, especially how Webhooks detect data and how recursive workflows function.
While experimenting with Webhooks and recursive workflows, after a few hours, I noticed I was being charged 10x more. I was on the Starter plan ($32/month), but yesterday I saw the charge had gone up to $400 (with no warning email received whatsoever). This was due to a non-stop ‘infinite workflow.’ Only then did I realise there were certain settings I needed to configure when using recursive workflows.
I found a setting under Settings > API > Infinite Recursion Protection to set the Maximum Workflow Depth, and it had a default value of ‘No Limit’. To be honest, I wasn’t familiar with that before this happened, and suddenly being charged 10x the amount was shocking. What if I hadn’t noticed and ended up being charged thousands more for just a few clicks? For Bubble to set the default to No Limit is unacceptable, especially since backend workflows are not easy to learn. By defaulting it to No Limit, it feels like Bubble is setting a trap for users, allowing them to profit from accidental overuse.
In my opinion, Bubble shouldn’t set the ‘Infinite Recursion Protection’ to No Limit by default. Instead, it should be set to a lower number, like 5k or 10k, and users should receive an email warning when they’re close to hitting the limit so they can adjust it.
I’m still waiting for the Bubble support team to respond. I’m concerned they might say this is my fault because they provide the settings for us to adjust, and that the charge is valid. I am extremely disappointed by this experience.
Problem is, if they set a limit and someone’s intentional workflow stopped working, there’d be just as many posts saying that they released a breaking change.
You don’t need to but they’re additional protections.
For new apps, yeah I agree, that’s a reasonable approach. (edit @sudsy says this is already the case)
Don’t worry! If this is your first time, they’ll waive the costs.
A couple of points about recursive workflows:
now schedule API workflow on a list is better, they’re rarely needed and you’ll find schedule API workflow on a list easier too (and faster, just generally all-around better)
when you do use them, it’s helpful to have a ‘count’ number parameter. When you reschedule it, set count to count + 1 (increase it by one each time). Have a condition on the schedule action that means it only schedules when count < {your tolerance limit e.g 10,000).
I created a new app last month, and it had a default limit. After attempting to reach the limit, I received an email notifying me that I was approaching the maximum limit.
you’re right, i’ve just receive an email, they said they offer a workload waiver for exceptional circumstances like these, i do appreciate it, but also it gives me an heart attack nonetheless
