Now that I have Sentry setup, I can finally gain some insight into some errors that I’ve been having. One that I can’t figure out that occurred 14 times yesterday out of 660 calls to a specific endpoint. The GET endpoint uses a single parameter (record Id) to retrieve info. For some reason those 14 calls did not have the parameter sent with the call.
The parameter is setup as a variable in WeWeb and is set to ‘Save in Local Storage’ and ‘Preserve on Navigation’. I can see the user workflow using the Sentry replays that there isn’t anything that I see clearing the variable before the call.
I’ve seen older posts saying that this is a Xano issue that upgrading from Launch to Scale fixed it? Is this still the consensus?
I believe the older posts you’re referring to had an Axios Error Network Error which is different.
Here it seems the error message mentions a missing parameter. This typically means you’re trying to make a request (usually a POST or GET) and you’re not sending all the required fields.
The missing field could be:
A query parameter (e.g., ?id=123)
A body parameter (e.g., { "email": "test@example.com" })
A path parameter (e.g., /user/{id} → /user/ is invalid without id)
Here’s how to identify the culprit:
Check in WeWeb:
Open the request setup (where you call the API).
Verify:
All inputs/variables are passed correctly.
Nothing is undefined or empty.
No typos in key names.
Test the workflow and look at the Logs: what does the payload look like? Is it sending the value it should be?
Check in Xano:
Go to the API endpoint in Xano.
Look under:
Input Parameters tab — are any set as Required?
Double-check spelling and case sensitivity.
I hope it helps. If you’re still stuck, please provide a short video or screenshots walking us through how things are setup on your side.
Hey Joyce, thanks for the reply. This has been a really hard one to debug, even with Sentry providing more context.
The endpoint has an input parameter that is the record id from my ‘checkups’ table. The function stack in Xano is just a Get Record using that id along with some addons to pull related data from other tables.
On the WeWeb side, I store the record id in a variable that is set when the user selects the record from a table list of records. It’s set to save locally and persist on navigation.
It works 99% of the time across dozens of users, nearly 1000 times a day. I don’t know if the parameter is getting reset prior to the fetch action or getting lost somewhere in the network transaction with Xano. I can’t find any action in WeWeb that would reset the value prior to the fetch. That’s why I’m thinking it may be a traffic issue with Xano.
Ah yeah, I hate those where it works 99% of the time because it’s so hard to reproduce the 1% of the time it doesn’t work!
I don’t think the preserve on navigation and save in local storage would be the issue (on the contrary, I would think that having both enables makes it even less likely that the variable is empty).
When you go to the Xano logs, do you see the call or not at all?
Check in WeWeb: