Kelvin Mulenga
I found the
I found the cause in the dev log: the Server Action was throwing TypeError: fetch failed, and Next surfaced it as the vague client error:
An unexpected response was received from the server.
I added guards so this now shows a normal admin form error instead of crashing the page:
Artist create/update/delete actions catch Supabase/network/schema failures.
The generic admin form catches rejected Server Actions and displays the message inline.
So if Supabase is unreachable, you’ll now see a useful message like checking Supabase URL/keys/connectivity. If the migration is still missing, it will show the migration-needed message.
Verified: