Bubble team should deploy all platform updates on off-peak hours

Right now they sometimes land in the middle of the day when everyone’s building or apps are live, and if something goes wrong it just causes chaos.

I get that it’s tricky since bubble’s global and there’s no perfect “quiet time,” plus the team needs to be around to fix stuff. But there’s gotta be some kind of solution, like choosing the lowest traffic window, doing partial rollouts first, or at least giving a heads up when something is going out.

Right now it feels like when an update misfires, it happens exactly when the most people are relying on the platform. Just seems backwards.

2 Likes

I’m sorry but this too is not acceptable.

You don’t push stuff to ‘live’ nodes and then 'see what happens’. And this seems to be Bubble’s approach.

1 Like

At least their inadequate QA would not be impacting peak hours. They need to do both, and starting with stopping deployments during peak hours would be very helpful.