URGENT ERROR: Unable to Fetch Collection

All of a sudden weweb is unable to fect a collection via a HTTP request - it was working fine, and is working fine in postman, so I cannot figure out why it isn’t working weweb. The call is not reaching my backend at all, the error is:

{
“data”: null,
“error”: {
“message”: “Cannot read properties of null (reading ‘id’)”
},
“type”: “single”
}

which isn’t making any sense as my backend is not being reached.

Any help anyone?

I should add this only happens when the source is set to dynamic; it works if I hard-code the values with static set. Note the details are the same so this points to an issue with WeWeb.

I am facing the same issue, also noticed that it only happens when fetching from a data collection, if I run the same query from a workflow, it works fine.

Looks like WeWeb changed something internally that is causing the issue.

Any luck on this? @nocodecreative.io

No there does not seem to be anything I can do to fix it. So my work can continue, I’ve change it to static data for now else I’ll be losing what little time I have waiting for some kind of support :pensive_face:

I have the same problem, it happens in Airtable collections.
Supabase and Xano collections there is no problem loading the data.

Same issue. This has broke prod. Highest urgency.

thanks for reporting it, we are looking into this

until we find the root cause, this fix has worked for some users: URGENT -- Weweb can't load collections? - #9 by BrancoDigital

Well, I suppose good to know it’s not just me being a noob. Though that was an infuriating two hours trying unsuccessfully to solve it. I’ll hang tight for a resolution.

It seems to work when you use the Rest Api node in a workflow. The issue only seems to happen in Collections..

Yeah, I can verify. Running it through the workflow worked. Though I definitely need the collection back, because all the logic for my app pivoted around that and I don’t want to go rewrite it just for this..

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.

@Raphael

This has been a very serious P0 incident. As a new customer, I have major concerns about the stability of the platform as a result. I fully understand that issues can arise and that things may slip through QA during a release—but the real concern here is the lack of communication.

It’s become quite clear that WeWeb does not currently offer 24/7 support and is unable to respond to urgent incidents promptly. This was first reported on Saturday, and it’s now Monday before we’ve even received an update, let alone a resolution.

What reassurances can you offer me, and other customers, that moving forward, critical issues will be addressed in a timely manner, regardless of when they are reported (including weekends)?

Best regards,
Wayne

They can’t.

Here is the full statement detailing what happened: