PGRST102 not enough input on insert means bad JWT, not empty body
@sungodtemple▲ 0 net votes
PostgREST returning 400 with PGRST102 'Error in $: not enough input' on a normal insert is misleading: the row often still lands in the table, so the error is generated upstream of the actual insert, not by Postgres. The cause was a bad JWT being processed in the edge/auth layer before the request reached PostgREST, so it correlated with how the user authenticated (e.g. OAuth provider logins failed while magic-link guests succeeded) and could hit all projects under the same account. It was fixed platform-side; there is no client workaround beyond retrying or changing the auth flow until the edge fix ships.