You edit a row in a Notion database, scroll up, and the view still shows a grayed-out row with a “Load More” button. This happens even though you just modified the database seconds ago. The root cause is Notion’s view-level row limit, which restricts how many items the page fetches from the server at once. This article explains why the limit overrides your recent edit and shows you how to expand the visible row set or adjust your workflow to avoid the issue.
Key Takeaways: Why Notion Hides Recent Edits Behind “Load More”
- View-level row limit (default 200): Notion loads only a subset of rows per view; rows beyond that count are collapsed under “Load More”
- Sort order and filter position: A recent edit may push a row to a position outside the loaded batch, causing it to appear unloaded even though the edit succeeded
- Manual “Load More” or page size increase: Click the button to fetch the next batch, or use the view menu to raise the row limit to 500 or 1000
Why Notion’s View Row Limit Hides Recent Changes
Notion databases display data through views — table, board, calendar, gallery, or list. Each view loads a fixed number of rows from the server in one request. By default, Notion loads 200 rows per view. This is a performance optimization: fetching thousands of rows at once would slow down page rendering, especially in workspaces with large databases. When you edit a row, the change is saved to the server immediately. However, if the row is not among the first 200 rows in the current sort order, it will not appear in the visible list. Instead, Notion shows a gray row with a “Load More” button at the bottom of the view. The edit is not lost; it is simply outside the loaded window. The same behavior occurs when you add a new row that sorts to a position beyond the current limit. The view does not automatically expand to include it. You must manually trigger a batch fetch.
Steps to Show Recent Edits Behind “Load More”
- Identify the view row limit
Open your Notion database in the view where the gray row appears. Look at the bottom of the page. If you see a gray row with “Load More” and a number (e.g., “Load More (42)”), the view has reached its current batch limit. The number indicates how many rows are hidden in the next batch. - Click Load More to fetch the next batch
Click the gray row or the “Load More” link. Notion loads the next batch of rows from the server — usually another 200 rows. Your recent edit will appear in this batch if it falls within the new range. Repeat this step until you locate the row. - Increase the view row limit permanently
To avoid this issue in the future, change the view’s row limit. Click the view name at the top of the database. Select “View options” or the three-dot menu next to the view name. Look for “Row height” or “Page size” — the exact label depends on the view type. For a table view, click the three-dot menu in the upper-right corner of the view, then select “Group by” or “Sort” and scroll to the bottom. Click “Layout” and find “Page size.” Change the value from 200 to 500 or 1000. Notion will now load up to 1000 rows in one fetch. Note: very large page sizes may slow down page loading on slower connections. - Adjust sort order to keep recent edits visible
If you edit a specific column frequently, sort the view by that column in descending order. For example, if you edit a “Last Updated” column, sort by “Last Updated” descending. This ensures the most recently edited rows appear at the top of the view, within the first 200 rows. To set the sort, click the view name, select “Sort,” add a sort rule, and choose the column and direction. - Use a filter to narrow the view
Apply a filter that matches the row you edited. For instance, if you edited a task with a specific status, filter the view to show only rows with that status. This reduces the total row count below the limit, making the edited row appear immediately. Click the view name, select “Filter,” add a filter condition, and choose the relevant column and value.
If Notion Still Hides Rows After Increasing the Limit
“Load More” button still appears after raising the page size to 1000
The page size setting applies only to the current view. If you changed the page size in one view but are looking at a different view (e.g., a calendar view instead of the table view), the limit reverts to the default for that view type. Switch to the view where you adjusted the page size. Alternatively, change the page size for each view individually.
Recent edit appears in a different database or linked view
If you edited a row in a database that is linked to another database via a relation or rollup, the edit may appear in the source database but not in the linked view. Linked views have their own row limits and sort orders. Open the linked view and repeat the steps above — increase its page size or adjust its sort order.
Gray row shows “Load More” but clicking it does nothing
This usually indicates a network delay or a server-side cache issue. Refresh the page by pressing F5 or Ctrl+R. If the problem persists, close the browser tab, reopen Notion, and navigate back to the database. The click should then fetch the next batch.
Notion Database View Row Limits: Default vs Maximum
| View Type | Default Row Limit | Maximum Configurable Limit |
|---|---|---|
| Table | 200 | 1000 |
| Board | 200 per group | 500 per group |
| Calendar | 200 per month view | 500 per month view |
| Gallery | 200 | 500 |
| List | 200 | 1000 |
Notion does not allow a page size larger than 1000 for any view type. If your database contains more than 1000 rows, you must use filters, sorts, or multiple views to keep all rows accessible without “Load More.”
The “Load More” behavior is by design — it prevents performance degradation on large databases. You can now raise the page size to 1000 or apply a descending sort on a timestamp column to keep recent edits visible. For databases exceeding 1000 rows, create a filtered view that shows only the subset you edit most often. This approach eliminates the need to click “Load More” repeatedly.