184

I am absolutely astonishing that in 2024 that a simple database update by AWS that was apparently incompatibly with the Bubble codebase results in so many Bubblers losing their valuable work. I find it even harder to believe that if Bubble truly had auto-upgrades switched off that an incompatible database update could knock out your whole platform.

It appears the resolution was a lazy “just restore to the last backup” before the auto-update occurred. This shows a complete disregard for those agencies that clients using their apps for business purposes and for the developers time who lost their valuable work. It doesnt matter whether it was minutes, hours or days, this is unheard of in 2024. Surely you took a backup of the databases before just reverting to a stale backup and would take the time to revert the update rather than just wiping out our work? Surely Bubble has a thorough roll-back plan for updates gone wrong.

How can your valuable clients have any confidence in your platform that if anything goes wrong (which is inevitable) that you dont just take the lazy way out and restore to a stale backup. I am truly astonished that this was the approach taken. Surely you at least took a backup of the broken databases before you took the lazy option and will work to roll-back the supposed auto-update by AWS and restore our work?

Form our perspective, we had several developers doing critical updates and our clients work that we have lost. The cost of our developers to redo their work is nothing compared to the reputation damage to our clients.

How can we continue to invest in Bubble for our clients, when you appear to have no roll-back plans for a simple database update when apparently auto-updates is switched off. It doesnt pass the sniff test. I have never experienced a data loss in at least 10 years. It just shouldnt happen. Can we please have some answers to ensure this wont happen again or what compensation are you going to offer for the lazy resolution.

8 Likes