I have managed to fixed the network error problem by optimizing the xano workflow. Xano told me that despite I don’t have rate limit on my plan there is cup constraint with my plan. Too complex workflow may lead to network error.
1 Like
Actually, I have the exact same problem. I tried to open a Weweb ticket but it’s hard to replicate the problem.
I can only pray that it’s not affecting end users.
I don’t think Xano is the problem, as my workflow is pretty simple in Xano, just save a record.
It’s very annoying because it happens randomly. Same thing is happening to me, nothing is sent to Xano. I can only see Network error on the Weweb debug log.
Again @raelyn, if its a network error it means the request was sent, we cant do much on our side. You can check in the network tab if the request was sent with the expected payload, at the expected endpoint, with the expected method, if all of this is good and sometimes it works and sometimes not its probably an issue on Xano side, please contact them, they may have access to more logs about your request
If you want to move forward please follow this guide showing you how to insepect network logs in your browser => Arc - Xano Auth | WeWeb - 10 January 2024 | Loom
You should be able to see the error status code
Thanks Alexis, really appreciate this, I will check out the link you sent… Thank you so much. 
Hello Raelyn,
I’m facing the same situation today with a lot of collections that used to work before and now they’re consistently through network errors. I’ll contact Xano but please post if you receive an answer.
Thanks!
I was checking with Xano. My issue was that I was fetching too many collections at the same time and the server couldn’t handle them. Check the Network tab of the developer tools of your browser. If you see that the collections that are returning errors are marked with a 502 you’re in the same case.
From my side, what I did was changing the order and putting them to fetch in series instead of parallel.
1 Like
I’ve been struggling with this too… is it possible that we all started experiencing this when it became possible to fetch collections in parallel in weweb?
Fetching too many collections at once could be creating an overload on the Xano server, yes.