For those interested in the Workflows performance in Bubble, as well as their cost-effectiveness in terms of Workflow Units. My task was to export 10,000 contacts from the Bubble database to the accounting platform Holded via API. I conducted an experiment using 1) recursive workflows and 2) schedule workflow on a list. As a result, the schedule workflow on a list provided performance and efficiency several dozens of times higher. The screenshot shows the Workflow Units spent on exporting about 4,000 contacts with multiple fields. Bubble wasn't boasting for nothing when they said they optimized the schedule workflow on a list.
Yeah, you're correct. But there are some cases where you can only use recursive instead schedule workflow on a list. E.g 1. When each item created/modified in the api workflow is dependent on the position or order they are in the list. 2. When each item (step 1) created or modified in the api need to modify the same item in step 2 (for example increasing a count field on that item based on the new item created in step 1) The single item will not be updated correctly if you use api on a list.
Yes. They even mention this explicitly in the docs now! schedule on a list has come a long way
Already knew, but WOW This really helps put things in perspective! 🚀
Product Story Teller and Manager | Rapid App Development Strategist | RPG Gamer for Life
3moTHUMB RULE: If you have to think for it and worry about it - its not ideal solution. Use supabase as your backend (and keep bubble as front-end) - You will never have to worry about these things. be stress free, live happily.