Ok, when you talk about the new integration itâs the wewebâs ?
With new integrations, I mean everything in the new tab Data & Api
Thatâs actually what I did, I used the new Supabase integration in the new tab Data & Api, but Iâm getting this issue
I am sorry but I am not sure to understand the bug you have, could you give us more detail? If you prefer to donât share detail here, you can send a message to the support and we will take a look
I always love improvements, but every openai call via the openai plugin has broke in PRODUCTION since this release went out.
We have not pushed anything to prod - wewebâs update caused this - this is a serious issue. Iâve submitted a bug but for everyone else using the plugin please check your production app.
Hi @bigduck, we are taking a look to your bug, we are doing our best to fix it as soon as possible. I will keep you updated when itâs fixed
If you have a look at my 2 previous replies first one at the bottom and the second reply. It might help explain the issue youâre having. Essentially thereâs 2 places to put in Supabase Integration stuff now but not very obvious that ones only for weweb backend and another is the old front end only way
2 Likes
@Joyce - Thank you i figured out the issue. My editor link changed from weweb-preview.io to editor.weweb.io and this impacted my CORS settings in xano. This would be helpful to know for users to update this if it is going to change. I might have completely missed it but I didnt see any communication regarding this when the release went out. Just wanted to share in case anyone else is experiencing this issue
1 Like
@Joyce - Regarding debug logs did the inline detail that used to appear in the log move somewhere else?
Previously, debug logs exposed detailed inline execution information for workflow steps. For example, I could directly inspect:
-
request payload/data
-
headers
-
query string
-
returned response/output
-
success/failure details
-
workflow completion trail
After the update, the Debug panel appears much more limited and now behaves more like a high-level activity feed. I can see that actions ran, but I can no longer easily inspect the same detailed inline logs that were previously available.
3 Likes
The log is very, very limited now.
Comment, but not a bug: Everytime I add a workflow somewhere I feel slowed down by the wizard. I understand it might be better for newcomers, but Iâd love a setting to not show wizard, and just create the action with defaults.
2 Likes
I have an open ticket with them regarding the new debug panel. Iâll forward them a link to your post as well. If you add a debug workflow element you can send whatever you want to the global debug panel but youâre the 4th person in 24 hours to post that we need the old detailed logs back.
A compromise would be to bring back the âverboseâ option and just have that show everything, but I also want that blue text payload structure back because the new raw json version is a pain on the eyes.
^ There is no way to resize the box in either of the above pictures. Was there something wrong with the old layout that prompted this change? Like maybe I am naive but who actually wants to look at the raw JSON like that?
This version was much better. It starts collapsed and omits all the unnecessary characters.
Ok thanks, it helps. So basically, if I want to use weweb as before the update, I will just use the âinterfaceâ tab, even for auth ? And never the âData & APIâ tab ? And if Iâve understood well, as soon as youâre using the âData & APIâ tab, youâll have to pay for an extra Cloud plan
And now my question is : where are the Auth elements (Sign in, Sign up forms, Forgot password etc), when using the âold wayâ ? I canât find them 
It could be handy to add an âAuthâ section here !
no, I didnt
I absolutely agree with you
@Raphael i meant file storage https://r2-calculator.cloudflare.com
also i`m having issues creating a table in a existing project
Honestly, i`m happy for the direction weweb is going, i really love how close to the community all staff are. But to me as a customer that has been stabed in the back by vendor lock pratices before (bubble.io workload units rugpull) that can change prices / processing cost at any time⌠its not a easy choice. So i`ll be testing as soon as this bug is fixed. But yeah, its hard to earn trust and easy to lose it.
please bring back the old logs filter⌠
3 Likes
Exactly 
Not necessarily
If youâre using âData & APIâ in an existing project that already has a plan, then yes, youâll have to get an extra plan. But if youâre using it in a project that doesnât already have a plan, then no: you can be on the free cloud plan.
If you want to try out the "Data & APIâ tab, we recommend you create a new project or try it in an existing project that doesnât have any plan attached to it.
Sorry, itâs not super intuitive 
Itâs a quirk due to technical constraints on our side
1 Like