Hi,
Just a quick followup on this thread. It is becoming extremely hard to get anything does as half the time the API requests fail since the endpoint has disappeared.
1 Like
Click on the plugin and just click continue, then go back to your endpoint and voila it’s back.
I’ve spoken at length to both Xano and Weweb and both are saying it’s each other. Right now I’m thinking it’s the plugin that’s not refreshing things correctly as I’ve made no changes to Xano and it happens all the time.
1 Like
I can get it back without issue but it will die again in a few hours.
It is impacting runtime and for me, the data bindings often have to be redone.
I don’t understand how this isn’t a P1 show-stopping bug given that it’s customer impacting.
@Toby007 POST is not writing to the db when the endpoint is disconnected.
Is that the request method you’re having trouble with?
Its not ideal, but what I did for my WeWeb and Supabase project (previously Xano) was just changing the collections from the native integration to Rest requests.
That usually works flawlesly as long as you parse the appropriate authorization headers if the endpoint is locked.
That should not break anything as long as you request the data in the same format, because you will be using the same collection.
1 Like
Thank you. I wasn’t sure if that would help so it’s good to have some confirmation.
Hope the learning curve isn’t super high for me.
1 Like
Hello, we are not 100% sure if it’s coming from us or from Xano. A dev of the team took a look last week and tried a fix. The fix has been released this morning. We can’t certify that it will fix the issue. Please tell us if you still have the issue or not
We hope that it will fix it and everything will work
1 Like
1 Like
WeWeb’s collection manager is pretty straight forward, so just make sure to check the syntax for each parameter and you should be up and running.
Good luck!