Hi @ZeroqodeSupport - thank you for the response.
A quick follow-up question, I have some workflows like this with Supabase error notification with condition of it being run only when it’s not live version. Do you know i this type of things is also eating into the load time?
Hi @steven.h.liu.1,
Good question! The short answer is: no, that specific workflow shouldn’t add to your load time in any meaningful way.
That workflow is an Element Event triggered by a Supabase fetch error — it only runs if and when the fetch fails. It doesn’t run proactively on page load. And since the condition is “Only when isn’t live version,” it won’t even fire in production at all.
That said, there’s a related point worth flagging. In your HAR trace, the user_profile query fires with an empty user ID filter (user_id=in.()), meaning it executes before the SupabaseAuth element has resolved a user. That query is likely returning an error or empty result — which would trigger your error workflow in dev mode. The workflow itself isn’t the bottleneck, but the query firing too early (before auth is ready) is a wasted round-trip. Adding a condition so that fetch only runs when the SupabaseAuth user ID is not empty would eliminate both the unnecessary request and the error.
One more thing that IS hurting your load time: duplicate queries. In the HAR I can see tag?select=* firing twice with identical parameters on the same page load. Each duplicate means an extra CORS preflight (OPTIONS) + the actual GET request — that’s 2 extra network round-trips for data you already have. Check if you have multiple SupabaseDatabase elements or workflows querying the same table, and consolidate them into a single fetch. Same goes for user_profile, which fires in two different forms. Every duplicate query adds ~200-500ms depending on network conditions.
Hope that helps!
Best regards,
Zeroqode Support Team
Browse all Zeroqode Plugins for Bubble
Hi @ZeroqodeSupport - thank you for the responses. I’m going through streamlining my app right now, and it’s definitely noticeably faster.
I do have another question that I hope you can help me with. I have a Supabase uploader in the reusable element; the path I set for it is [page’s user_id; this is a custom state]/event/.
However, when the file is actually uploaded and saved, it would skip out on the user_id and directly go to /event/, so a completely different file path (see video below). The exact same setup works when the uploader is stored in a page vs. reusable. The reusable element is a group.
I recorded a video to showcase this (Google drive LINK)
Hello @steven.h.liu.1 ,
This is a situation that we see very often with the reusable element, since in Bubble the reusable seems to not have direct access to page-level data right away.
It is a simple timing/sequencing issue.
When the uploader tries to resolve page's user_id (your custom state), it returns empty/null inside the reusable element — so the path collapses from {user_id}/event/ to just /event/ .
You can try the following approach: pass the value into the reusable element
user_id, type: text) or use the reusable’s Content Type to pass data in.user_id custom state (or data source) to page's user_id.page's user_id:This ReusableElement's user_id/event/
Let me know if this resolves the issue for you.
By the way, we’re glad to hear that streamlining the app helped with the performance. Dont worry if you’re not hitting expected timings right away - sometimes it’s a matter of trusting the process.
Best regards,
Zeroqode Support Team
Browse all Zeroqode Plugins for Bubble
Hi @ZeroqodeSupport - I have a Google auth situation. I recently created an independent separate sign-in page. However, when I went through the sign-in and got redirected to url, the session wouldn’t stay signed in
___________________
EDIT1. I also sent you a video via DM (due to personal email addresses) to explain the situation more clearly.
EDIT2. It seems if I redirect back to my “sign-in” page first vs. home_page, the auth would happen and continue to persist across the pages, but if I redirect to home_page, it wouldn’t recognize the authentication session
Hello @steven.h.liu.1,
We’ve received your message and are reviewing the video along with the screenshots.
Since the discussion may involve sensitive data, we’ll make sure to respond via DM.
Please bear with us while we review the setup.
Best regards,
Zeroqode Support Team
Browse all Zeroqode Plugins for Bubble
Hi @ZeroqodeSupport - quick questions.
Hi Steven,
Thanks for reaching out! Here are the answers to your questions:
Regarding Question 1: This seems to lean more toward a general Bubble data formatting question rather than being specific to the Supabase plugin’s functionality, but I am happy to help point you in the right direction.
Could you clarify what you mean by reading it correctly? Are you trying to display the extracted ‘content’ of the JSON without the raw formatting?
For example, instead of displaying the raw data like this:
[
{
\"message\": \"message 1\"
},
{
\"message\": \"message 2\"
},
{
\"message\": \"message 3\"
}
]
…are you trying to parse it to return just a clean list of texts: “message 1”, “message 2”, “message 3”? Let me know what your exact end goal is for the frontend, and I can suggest the best Bubble approach.
Regarding Question 2: You can definitely do this! You can find the relevant documentation for this action here: Server Side Actions - Run SQL Query.
The ‘Run SQL Query’ is a workflow action, which means it executes and returns a payload immediately within that workflow. To display the JSON on your frontend without saving it to the Bubble database, you simply need to grab the result of that action in a subsequent step.
For example:
Step 1: Run SQL Query.
Step 2: Reference Result of step 1 (Run SQL Query’s Result (JSON)) and pass that data to your UI.
You can pass this data by using the “Display data in group” action to send it directly to a visual element, or by using “Set state” to save the JSON to a Custom State on the page. Your frontend elements can then just read dynamically from that group or custom state.
I hope this helps! Let me know if you have any other questions.
Best regards,
Zeroqode Support Team
Browse all Zeroqode Plugins for Bubble
hi @ZeroqodeSupport - appreciate the help.
Re: Q1. I have a “jsonb” column in the Supabase table with clean formatting (see below for sample json payload). I understand Bubble always require us to specify the json structure in order to read it, so I assume as long as I specify the structure as such in API connector, Bubble will be able to read the json?
{
"account_id": 1,
"start_date": 20240401,
"duration": 30,
"metric_type": "engagement",
"platform_id": 1,
"audience_demographics": {
"age": {
"18-24": 28,
"25-34": 311,
"35-44": 105,
"45-54": 12,
"55-64": 8,
"65+": 3
},
"gender": {
"F": 388,
"M": 101,
"Other": 73
}
}
}
Q2. Do you mind clarifying a bit more? I am a bit lost at this step of the setup (backend workflow- see pic):
Also, if I end up getting the json payload via the SQL query (similar to above), how would i parse the json into something Bubble can read? (i assume it’s just specifying the top section of the “Run SQL query”- see last pic)
________________________________________
EDIT1. I used Run SQL query on the backend because i don’t want to expose my access key in the frontend.
EDIT2. Could I use RPC to achieve what I want to achieve vs. SQL query management?
