Hi,
my app is unavailable; no data is retrieved.
In the editor, all connections with Airtable are still there, but when fetching data, I get this message :
What’s going wrong?
Same issues here, no support from WeWeb for way too long.
5 Likes
Honestly, the fact that this has gone on all day without a single comment from anyone at weweb is disconcerting
3 Likes
I agree, very concerning indeed, as a new paying customer, building production apps for clients, this is a major concern.
6 Likes
Same here. FWIW, REST API connections that do NOT bypass CORS seem to work fine.
Currently considering testing supabase edge functions instead of direct REST API calls through weweb, might help.
2 Likes
The issue is most probably WeWeb’s servers and any collection which is routed through them. It seems like WeWeb is falling apart lately more than usual. It’s actually bad that they don’t have on call engineers during the weekends..
4 Likes
Same issue here. Has anyone solved?
1 Like
I think only WeWeb can solve this tomorrow, or at least they’ll hopefully start tomorrow..
My current solution:
- Supabase auth and tables started working after resetting to a previous editor state
- Disables “Proxy request server side (bypass CORS)” for REST API data collections, fixed most of my data collections this way
- For those that didn’t, such as custom fly.io microservice calls, created Supabase Edge functions to call these APIs instead
I was able to restore most of my platform’s functionality this way, hoping this won’t break again when weweb fixes the core issue!
2 Likes
This largely worked thank you!
1 Like
We are looking into this, @BrancoDigital’s solution have worked for users affected, thanks for sharing it. If you are affected please consider resetting to a previous editor state (rollback to a previous version). We hope to have this solved within the next 12 hours.
We take this issue very seriously and will share a detailed post-mortem once we’ve identified the root cause.
1 Like
I’m rather new to Weweb.
How do I reset to a previous editor state (rollback to a previous version)?
(I have the free plan)
12 hours!!! You should have started fixing this last Saturday when the error occured…
3 Likes
This is a big problem, that occurs again and again.
We have a webapp and the production state is influenced by internal weweb errors that seemingly appear on nearly every update weweb makes.
This is a huge problem! It can not be that without further editing or releasing new versions of our webapp, the functionality of the app changes and new bugs appear.
I can not imagine how much of a problem this is for businesses with huge traffic and sales volume.
Please change something about your internal release process or QM.
This is a dealbraker and huge company risk for you as well.
1 Like
For real. It’s one thing for things to break while in the build stage - but for a locked and solid deployment that’s publically available to go dead with no warning is terrifying.
I get that sometimes things break when you’re constantly working to improve a product. Goodness knows I’ve broken more than my share of things and upset customers because I didn’t catch an error until too late.
I wonder if it’d be possible to put the power of updating into developers hands. For example, a new version is released, we’re notified, and can choose when to roll it out. And can roll it out in a test environment first to make sure everything works before we deploy it to our projects fully. Even if we’ve only got a buffer of a week or two before we have to upgrade that would give a lot more people the time to ensure things are working before committing to an update - and also give WeWeb time to discover bugs from us and fix them.
At the very least notifications of when WeWeb are going to push an update so we can be ready to make sure nothing is broken once they do, and get ahead of problems. And also notifications of known bugs. Those two things would at least give us something to work with and maybe preemptively put out customer fires.
1 Like
Thanks for the response to this post, but I still have a serious reservation… As a new user of Weweb, I already received a lot of help from the team and from the community. So thank you for this.
I assume that every update of your systems is thoroughly tested in advance and a bug is always possible. But what is happening now seems to me to be a misjudgment of an update error and its consequences. The fact that no one from the team responded to chat, messages in the forum, etc. during the weekend seems like concealing a known problem. Only when the community starts posting a lot, the announcement comes that the problem is taken seriously.
In crisis-management, it is important to admit a mistake if necessary, but above all to COMMUNICATE IMMEDIATELY AND OPENLY. That in itself does not solve the error, but by passing on a state of affairs in the community for almost an hour by hour, it shows the concern for the user.
I hope this problem gets solved within a few hours, but I merely hope for a more open communication on later issues.
3 Likes
And I think it can not be repeated how important this is.
It is so much of a reputation killer and dealbreaker, that if I were in your shoes - I would halt all further updates and new functions until a new more secure ways of handling changes to the platform is implemented.
Before we like fancy features, we need to have a reliable platform. This is not a beta-stage for the company.
3 Likes
Preach. Stability first please and thank you.
1 Like
The problem is fixed for every application not using the SQL plugin. We are now working on a fix for applications using this plugin. We’ll keep you updated.
2 Likes
Thanks! Back up and running here.
2 Likes