Skip to main content

Why does my Big Table show a different row count than what's actually in the grid?

If the number shown next to your Big Table name doesn't match the rows you see in the grid, don't worry, this is expected behavior, not a bug.

The short version: The number next to the table name is a quick running estimate. The rows you actually see in the grid are the real, current contents of your table.

What's actually happening

The count displayed next to the table name is a running tally that can include recently deleted rows that haven't been fully cleared out yet. The rows visible in the grid reflect your table's true, current contents.

Why does Glide do it this way?

Big Tables are built to handle very large datasets quickly. To keep things fast and avoid slowing down your app every time someone opens the editor, we don't recalculate every row in real time. Instead, we keep a lightweight running total that updates as the table is used and gets fully reconciled in the background on a regular schedule.

For tables with millions of rows, recounting on demand would make the editor noticeably slower β€” so this trade-off keeps your experience snappy.

What to trust

Treat the number next to the table name as a quick estimate. For the accurate, current row count, rely on the rows you see in the grid itself. The running tally will be automatically caught up during the next background reconciliation.

Did this answer your question?