Hi all - it seems like its a well known fact that Bubble can’t handle concurrent updates well as there is no consistency as to what will get updated in what order.
I’ve tried breaking everything into chunks and scheduling it through back end workflows but even then its not consistent and I have to adjust the delay between calls to get it to work. And even then, who knows if if will act the same way in production?
Is there another trick or workaround to ensuring data gets updated consistently?
Generally speaking, using custom events and/or Result of step x should accommodate many scenarios. Database triggers come in handy at times as well. It really depends on exactly what you’re trying to accomplish. The devil is in the details, and each use case requires special consideration.
The first step, however, is making sure you’ve read and understand the workflow execution rules. If you’ve already done that, then sharing additional detail might enable others to offer specific suggestions.
Interesting read, hadn’t seen before. Wasn’t aware that actions called within a custom event will finish before calling another custom event.
