The project is now restoring (COMING_UP). Let me wait for it to come online, then verify the startup_applications table exists with the right columns.
The project is back online, but there are no tables at all — startup_applications and pitch_deck_requests don't exist. That's the real cause of the save failure. Let me check exactly what columns each insert uses before creating them.
Now I have both table shapes. The startup_applications insert uses the service-role admin client (bypasses RLS), while pitch_deck_requests uses the browser anon client (needs an insert policy). Let me create both tables.
The tables are now created. Let me verify everything is in place.
Fixed. The root cause was that your Supabase project had been paused (auto-paused after inactivity), and on top of that the two tables the forms write to didn't exist yet. Here's what I did:
startup_applications (the founder "Get help closing your round" form) with all columns the server action writes: name, email, company_name, website, stage, round_size, message, source, user_agent, referrer. RLS is on and writes go through the service-role admin client.pitch_deck_requests (the investor "Access Pitch Deck" form) with name, fund_name, email. Since that form submits from the browser via the anon client, I added an insert policy allowing anonymous submissions.Both forms should now save successfully. Note: if a Supabase project stays inactive for a long time it can auto-pause again — if you ever see this error return, that's the first thing to check. Go ahead and test the form submission now to confirm it saves.