Running multiple backend workflows

Absolutely, happy to help and share ideas!

It’s been quite an experience building and managing our own app, and such a mix of emotions (I have genuine empathy for programmers now that I’ve had similar first-hand experience!). It’s wonderful being able to test new ideas so easily and create something useful, but there’s also that constant worry of ‘breaking’ it or missing something important. We actually had a problem happen with our very first client, which prevented them from accessing the app at all. It was very embarrassing, and this was when we were relying on another Bubble expert, so we couldn’t fix it until they were available. On the bright side, it motivated us to learn Bubble ourselves and we haven’t looked back.

I’ve also been coming to terms with the fact that there’s always something new to learn about Bubble, and that there aren’t clear best practices (maybe there should be) other than those you pick up by reading through the forums. For example, a singular ‘step-by-step guide to creating a resilient recursive backend workflow’, including how to use commands like ‘only when list minus: list item#1: count > 0’ to tell Bubble when to repeat the WF. I couldn’t believe it when I found that post - we were doing it a different way previously, so had to rebuild that process! :slight_smile:

In fact, it’s the same with @lottemint.md passing along the helpful advice about API logs that he happened to hear from another Bubbler, and that @NigelG has been using. Makes me wonder - why isn’t this a documented best practice?

My best advice to anyone is to read read read the forums and make sure to do extensive testing before rolling out any new features. And, of course, to build in those failsafes we talked about, so that you’ll know when something breaks and how to fix it. Also, read The Ultimate Guide to Bubble Performance - 156 pages of optimizing tips, which is a best practice guide written by @petter. Btw, @petter , let me know if you’re ever offering an app audit service, as we’d love to have an expert review and optimize our app :slight_smile:

2 Likes