Hi, I have a workflow where Fetch collection seems to not be working. In Xano, the test on it work fine. When I fetch from weweb its telling me there is a 401 code, which means the authentication token did not pass. But I know I am authenticated by looking at other areas of the app that require it.
Here is a screenshare showing my setup:
Did you bind the ‘notes_id’ under collections to the URL you are fetching from Xano?
Url has to be /notes/{bind your variable here}
And also it’s expecting a meditation id in Xano so make sure you have that too
Where do you bind it? I didnt think I’d need the ‘notes_id’ because when I test run it in Xano all I have to do is enter the meditation_id and the auth user and it works. I don’t give it a notes id as an input.
If I’m supposed to in Weweb do I set that up as a header?
Actually, I fixed it by completely changing how I was looking it up. I Couldn’t see the forest through the trees and I made it m ore complicated than it needed to be lol
Hello everyone,
Still no explanation or solution to this problem?
I suspect a bug between Xano and Weweb in Xano plugins.
On my end, I have a notification system, including an API call to check the number of unread notifications. On Xano’s side: Query all records where notification.user_id == auth.id AND readed_at == null, with an output of type COUNT.
When I have unread notifications, everything works fine.
However, when I have no unread notifications, Xano correctly returns 0 without any issue, but Weweb throws a 401 error.
Why?