LogicTrail
  • Trails
  • Check my app
  • Pricing
  • Sign in
  1. Trails
  2. /
  3. Data you can lose
  4. · 4 minutes · Pro

Exactly 1,000 orders

Your admin dashboard says you have 1,000 orders. It has said exactly 1,000 for three weeks.

This answers: Why does my Supabase query return only 1000 rows? No coding needed. 3 quick decisions.

  • Keeping data safe
  • How a request travels

Checking your access…

Why does my Supabase query return only 1000 rows?

's returns at most 1,000 rows per request by default, and it does not raise an error when it stops. Ask the database to count instead of downloading rows, and when you need every row, with a stable order such as created_at then id.

Trail of the bug
  1. Browser
  2. Your server
  3. Database

Breaks at Database: Silently capped at 1,000 rows

Why AI tools write this bug

Generated dashboards often load a whole table and count it in the browser, which works perfectly in testing with a few hundred rows.

How to fix it

  1. Use a count query instead of counting downloaded rows.

3 more steps, and a prompt that checks your own app for this bug. Part of Pro.

Unlock

Common questions

Should I just raise the row limit?
No. Every visit would download far more data, and it breaks again at the new limit.

Related scenarios

  • Invoice 105Free · 4 min
  • The save that saved nothingFree · 4 min
  • The key in the bundleFree · 4 min

More on this trail

Data you can lose: Agents that reset production, backups that are a day old, rollbacks that break.

Want someone to look?

We check AI-built apps for this and three other common leaks, in plain English.

Check my app
Sign in

Sign in to walk this one

3 decisions, about 4 minutes, and a prompt to check your own app for the same problem.

Sign in No password. We email you a link.

How to fix it

  1. Use a count query instead of counting downloaded rows.

3 more steps, and a prompt that checks your own app for this bug. Part of Pro.

Unlock