Performance smoke
List endpoint without a page size
An endpoint returns every row in the table, which works in development and fails at the first real customer.
Termscritical flow (a path a user takes that costs money or trust if it breaks: sign-up, checkout, invite, export) · staging environment (a copy of production, without customer data, where release candidates are tested) · migration (a scripted change to the database schema that ships with a release and should be reversible)
mediumseverity if found in a releasesources verified 2026-09-21
Why AI-assisted code produces it
Pagination is a requirement that has to be stated; the generated default returns the whole collection.
AI-co-authored pull requests carried 10.83 issues each against 6.45 for human-only pull requests, about 1.7 times more, in a sample of 470 open-source GitHub pull requests (320 AI-co-authored, 150 human-only).
Source: CodeRabbit, 2025-12-17 · verified 2026-09-21
How we detect it
Call each list endpoint with no limit and with an absurd limit.
Most associated with
Tools: Cursor, GitHub Copilot, Claude Code, Windsurf, Lovable, Bolt
Checklist items that catch it
List endpoints are paginated and bounded
automated Request each list endpoint with no limit parameter and with limit=100000.
Every list endpoint returns at most its documented page size in both cases.
Dots: Starter, Growth, Scale. The item runs on every release for the plans marked.
More in performance smoke
- medium
- medium
Check your codebase for this pattern
The coverage audit lists which catalogue patterns apply to your critical flows. 5 business days, $1,200, credited to a first month.