Capacity check

Use when: "why aren't new rows being added?", "why is the import stuck?", "is this table full?", or any question about rows failing to appear. Check capacity before assuming a run, config, or enrichment problem — a full table silently stops accepting rows, which looks like a broken import.

Scope: regular tables only. Archive tables are not subject to this ceiling — if the user points at an archive (tbl_... that came from another table's archive.tableId), say the check doesn't apply and redirect to the parent table.

The rule

A Clay table stops accepting new rows once it reaches its row ceiling. The ceiling is 50,000 by default, but it is plan- and table-dependent — plans can set it lower, and per-table overrides can raise it — and the CLI does not expose the effective value. The same ceiling logic applies to:

• rowCount — the table's own row total (clay tables get). At the ceiling, the table won't take new rows.
• each source's numSourceRecords — a source feeding the table, read from the table's source columns (clay tables columns list → sources[] on each source column). A capped source can't push more records in, even if the table itself has room.

So the table is constrained if rowCount OR any source's numSourceRecords is at its ceiling. Evaluate every source, not just the largest.

Procedure