Fede here, sharing a reminder on scheduled database maintenance for this coming weekend. This will sound familiar because it’s the same work that was planned for the March 6-7 weekend. Unfortunately the team had to abort that last upgrade attempt and will instead do it during this maintenance window.
side note: we originally planned this new attempt Friday-Saturday like the last one, but moved it to Saturday-Sunday to help @pedro5 host his Saturday morning Bubble workshop for entrepreneurs as part of SABRAE’s “startup day” in Brazil
What’s happening
We’re upgrading our Postgres databases. AWS is ending support for the version we currently run, so this upgrade is necessary to keep your apps running reliably on supported infrastructure. It’s a routine but important change, and we want to be upfront about what to expect.
When the maintenance takes place
Starting: 5PM ET on Saturday
Ending: 11AM ET on Sunday
What will be affected
During the maintenance window, schema changes will be blocked. That means you won’t be able to:
Add or modify data types or fields in the editor
Deploy apps, either through scheduled security dashboard deployments or through the editor
Deploy previously changed types
Copy, delete, or transfer apps
Create apps from a template
If you try to do any of these things during the maintenance window, you’ll see an in-editor notification letting you know that the action is temporarily unavailable.
What will NOT be affected
Your live apps will continue to work normally. All standard data operations — creating, reading, updating, and deleting records — will keep running as usual. Your end-users shouldn’t notice anything.
In short: If you’re not making structural changes to your database you likely won’t be affected at all.
What you should do
We know Bubblers build at all times of day every day of the week, so we appreciate your patience as we keep things running smoothly behind the scenes. If you have any questions, feel free to drop them below.
Fede, moving it to help pedro5 host his Bubble workshop will wipe out Monday for anyone in APAC - why not schedule for 5 pm Friday - per a normal update and get Pedro to move his workshop to the next day and you accommodate those of us who are not in the US and will have to work Sunday to accommodate.
This crashed one of our critical apps the last time even though it wasn’t supposed to have any impact. All of our data records disappeared for many hours.
Can this effort really not be performed offline and brought into production via syncing? That’s what we do with Postgre updates. An outage of this magnitude for this duration seems very inconsistent with Bubble’s desire to be a capable and reliable hosting platform.
During the last scheduled maintenance the team discovered a series of problems that affected a small number of app during the process. This is one of the reasons they decided to cancel the upgrade and try again after investigating the issues.
Unfortunately this is not possible with the type of scale and operations we support.
By any chance the end has been moved by an hour? Because from the status page the maintenance seems to be over but in my app the notice has changed and the end of the maintenance has increased by an hour..
I have the same issue and I cannot edit or update any datatypes but the status page is mentioning that they are fully operational. Please have a look and update us asap. Thank you
@Fede.bubble what’s going on here? The maintenance was scheduled to finish an hour and 12 ago. Then it was moved by an hour and yet the notice still does not disappear internally to the apps. I understand the unexpected and I understand that it’s Sunday but we also plan distributions during the weekend here. It would be the case that incident.io in the meantime reflects the real state of affairs and it would also be useful to have updates if the deadline is postponed..
P.S. now it says that the maintenance will end in an hour.. what game is it?
Hey @mario11, the team tells me that we are nearing the end of maintenance process. Four of the five remaining databases are on the final stretches, and the last is not far behind.
Engineering decided to extend the maintenance window a bit to finish everything off
