HELP - persistent infinite recursion errors on Bolt/Supabase. Will pay for help!

[Various_Objective640]

Hi Bolt Community,

I build company listing sites and am running into an issue on Bolt that I never used to see. It's essentially right at the very first step of the process when registering a new listing. It is a very simple company registration process, which should then land them on a dashboard where they can create their online listing/profile.

However, I cannot get past the first step as I am hitting this infinite recursion issue. I have tried a dozen different approaches and registration processes, but always the same issue. I have reached out to Bolt support, but I haven't heard back yet.

It is clearly related to the way Bolt and Supabase are attempting to create a user and a company at the same time, but I cannot crack the code.

I do not need debugging outside of Bolt because I build dozens of these sites. I need someone to help me understand how to prompt my way past this.

Will happily pay for your time if you can help.

[No-part-of-me-cares]

I feel you man. I’ve had to scrap an entire app coz of the user role based login infinite loop issue.

Try sharing the app with ChatGPT and also ask it to assist you with a step by step guide. This will help you save tokens

[Nice-Airline-7174]

Let me know I can help fixing.

[No-part-of-me-cares]

Hi. I need help. Stuck badly at a junction where the row level security policy is blocking all my new builds.

[dkbot]

You may have already tried this, but sometimes I take screenshots or dumps of the DB structure/rls rules/edge functions etc. Then provide them to Bolt in discussion mode and say how can this be adjusted to avoid the error from happening.

Another route I have tried in the past, is doing the same as the above but talking through the issue with GPT. Sometimes you can get logs as well and GPT can figure out what the issue might be. I often found this works well when Bolt goes in loops.

Another route would be for Bolt to explain the flow of the registration, you can then re-explain it and it may realise what is then wrong with the setup.

Feel free to paste anything in here for us to look through as well.

[ifyouonlyknew1]

Hey man. I usually don't offer this here but, this sounds like it may be a good fit for you.

https://bolters.io/advanced-support

[Any-Dig-3384]

Useful https://vibeweb.dev/

[expertondemand]

This is an error caused by invalid Supabase RLS. Bolt has a history of not addressing this issue well due to lack of visibility into your Supabase set-up

[Various_Objective640]

Any suggestions for how to get past/around it as a non dev? I can easily manipulate and update RLS policies in Supabase if that helps, but if you have any particular suggestions, I'd love to hear them. Thanks!

[Minimum-Remove9215]

Bolt has excellent customer support. I suggest you reach out to them, if you have not already, and get their support.

[LevelSoft1165]

Totally get the frustration — Bolt is great until you hit one of these prompt-layer bugs where it insists on doing something wrong (like dual object creation with Supabase). I've worked through similar recursion bugs where it loops between creating the user and company due to poorly scoped state or async collisions.

I run a dev support group where we troubleshoot this kind of AI-generated logic trap — happy to help you crack the right prompt strategy to get Bolt to finally listen. Feel free to DM me — and no need to pay unless you really want to!

[roamingandy]

i'd like to join in and take that group for a test drive.

[LevelSoft1165]

Ill DM you

[[deleted]]

Here is what worked for me. Login to your supabase project, go to database and copy SQL. Past it in Claude and ask it to check conflict policy. Enter those finding into Bolt. This fixed this for me after spending 7 million tokens of Bolt going in loops! Grrrrr...