Supabase.js Error 413 on `select`

I've got a fairly simple schema which is giving me a

when I try to query it.

...
  // 413
  const { data, error } = await supabaseClient
    .from<Row_Heartbeat>('heartbeats')
    .select('*')
    .eq('application_id', applicationID)
    .order('created_at', { ascending: false })
    .limit(27);

  if (error) {
    throw error;
  } else {
    return data;
  }
...

...
  // 413
  const { data, error } = await supabaseClient
    .from<Row_Heartbeat>('heartbeats')
    .select('*')
    .eq('application_id', applicationID)
    .order('created_at', { ascending: false })
    .limit(27);

  if (error) {
    throw error;
  } else {
    return data;
  }
...

The query works fine in the SQL editor (https://storage.queue.bot/t/930bm9voa.png).

There is no documentation on 413 in any docs, GitHub issues, or help channels on Discord. I have three questions

1) What does this error mean in the context of Supabase? I know HTTP 413 is "request too large"
2) How can I troubleshoot/fix the problem?
3) What caused the problem?

Supabase•4y ago•

8 replies

jeffreyhugh

Supabase.js Error 413 on `select`

I've got a fairly simple schema which is giving me a

when I try to query it.

...
  // 413
  const { data, error } = await supabaseClient
    .from<Row_Heartbeat>('heartbeats')
    .select('*')
    .eq('application_id', applicationID)
    .order('created_at', { ascending: false })
    .limit(27);

  if (error) {
    throw error;
  } else {
    return data;
  }
...

...
  // 413
  const { data, error } = await supabaseClient
    .from<Row_Heartbeat>('heartbeats')
    .select('*')
    .eq('application_id', applicationID)
    .order('created_at', { ascending: false })
    .limit(27);

  if (error) {
    throw error;
  } else {
    return data;
  }
...

Supabase.js Error 413 on `select`

Similar Threads

Supabase.js Error 413 on `select`

Similar Threads

Similar Threads

Similar Threads