@Raphael
This incident makes it clear that your update deployment process needs a serious reevaluation. Such an outage is unacceptable for any platform hosting production applications. We cannot continue to rely on a service that risks prolonged downtime without clear rollback mechanisms or communication.
We’d appreciate it if you could share how you plan to address this issue and prevent such incidents in the future. Otherwise, we may be forced to migrate to a more stable—if less innovative—solution. Reliability must come first.
This should have the highest priority, and I think how you (weweb) will handle this community feedback and address this issue can have a large impact on further winning or loosing customers for this otherwise really amazing product-idea you have already built.
They won’t handle it in any special way as usual I think. We’ll be glad if we get any info on what actually happened. Then the people will go on with their builds until it happens again soon.
I’ve seen it a couple times before, they don’t change anything regarding their real problems… they focus on their not even working AI… This was the last time for me to be honest. I’m out.
Never push a build on a Friday. Even in companies that have live human 24/7 support - you never have full engineering resources on a weekend.
Never push a build on a Friday. This should be policy IMO.
Further, when XANO pushes a new release - it does not go to every single user at the same time - not sure if it’s geographic or how they do it - but WeWeb needs to find a way to roll out to a batch of users before all users - because breaking changes on a new release is almost predictable at this point.
I suspect what does not get QA’d (or QA’d enough) on new releases is how the new changes play with various plugins. WeWeb definitely knows how many of which plugins are in use - so, would not be hard to prioritize QA with test projects that are set up with the most used plugins - or any plugin for back end communication.
As this thread makes clear, something has to change — otherwise, customers will churn as quickly as they’re being onboarded.
I don’t think anyone here means this in a negative way, but recent experiences have shown that this is a make-or-break issue that needs attention and communication from WeWeb.
If we didn’t care about WeWeb, no one would bother writing in this thread — we’d simply leave.
So please, WeWeb team: take this seriously and make things better.