Fix Notion ‘Cannot Load View’ Error on Filtered Database Refresh

When you refresh a filtered database in Notion, you may see the error message “Cannot Load View” instead of your data. This error usually occurs because the database contains a large number of items or because a complex filter is trying to compute across too many database properties. This article explains why this error happens and provides step-by-step methods to fix it so you can view your filtered data again.

The root cause is that Notion’s web-based rendering engine can time out when it tries to apply a filter across thousands of items or across deeply nested relation properties. The fix involves reducing the database size, simplifying the filter, or switching to a linked database view. By following the instructions below, you can restore your database view and prevent the error from reoccurring.

This guide covers the technical reason for the error, three proven methods to resolve it, and additional steps to take if the error persists after applying the main fix.

Why Notion Shows “Cannot Load View” on Filtered Databases

Notion stores database data in a proprietary JSON-based structure that is rendered in the browser or the desktop app. When you apply a filter, Notion must scan every row in the database, evaluate each filter condition, and then render only the matching rows. If the database contains more than approximately 5,000 items, or if the filter references rollup, formula, or relation properties that themselves depend on other databases, the render engine can exceed its processing time limit. When this happens, Notion cancels the rendering and displays “Cannot Load View” instead of your data.

Filter Complexity and Property Types

Filters that use multiple “and” or “or” conditions force Notion to evaluate each condition sequentially. Rollup and formula properties are especially heavy because Notion must first compute the rollup or formula value for every row before it can apply the filter. For example, a filter that says “Show items where Status is ‘In Progress’ AND Priority is ‘High’ AND Assigned To contains ‘Jane'” requires three separate scans of the database. If any of those properties is a rollup from another database, the scan time multiplies.

Database Size Thresholds

Notion does not publish an exact row limit, but testing shows that databases with more than 10,000 rows are at risk of this error when a filter is applied. Databases with fewer than 2,000 rows rarely encounter the error. The error also appears more frequently in the web browser than in the desktop app because the browser has stricter memory and CPU limits.

Steps to Resolve the “Cannot Load View” Error

Use the following methods in order. The first method usually resolves the error. If it does not, proceed to the second or third method.

Method 1: Simplify or Remove the Filter

1. Open the database view that shows the error
   Click the view tab name at the top of the database. If the view does not load, switch to another view that does not have a filter, such as a default “All” view.
2. Click the Filter button
   In the top-right area of the database, click the Filter button. A filter panel opens showing all current filter conditions.
3. Remove one condition at a time
   Click the X next to each filter condition to remove it. After removing one condition, click outside the filter panel to see if the view loads. Repeat until the view loads successfully.
4. If the view loads, reapply a simpler filter
   Add back only the most essential filter condition. For example, instead of filtering by three properties, filter by just one property. Use a “Select” property rather than a “Rollup” or “Formula” property if possible.

Method 2: Duplicate the Database and Apply the Filter

1. Duplicate the entire database
   Hover over the database title at the top of the page. Click the three-dot menu icon and select “Duplicate.” Choose to duplicate the database with all content. This creates a fresh copy without any view corruption.
2. Open the duplicated database
   Navigate to the duplicated database. It will appear below the original page by default.
3. Apply the filter again in the duplicate
   Click the Filter button and add the same filter conditions you used before. If the duplicate loads correctly, the original database had a corrupted view. You can delete the original database and rename the duplicate.

Method 3: Use a Linked Database View Instead of Filtering Inline

1. Create a new page for the linked view
   Create a new page in your workspace. Give it a descriptive name such as “Filtered Project List.”
2. Add a linked database block
   On the new page, type /linked database and select “Linked database from” then choose the original database from the list.
3. Apply the filter to the linked database
   Click the Filter button on the linked database block and add your filter conditions. A linked database view renders separately from the original database and often avoids the timeout error because it loads a lighter dataset.
4. Set the linked view as your primary view
   If you prefer, rename the original page and use the new page with the linked database as your main working view.

If Notion Still Shows “Cannot Load View” After the Main Fix

Database view still fails after removing the filter

If the error persists even after removing all filters, the database itself may be too large. Archive or delete old rows to reduce the total row count below 5,000. To archive rows, create a “Status” property with an “Archived” option, filter for that option, and delete those rows.

Error appears only in the web browser but works in the desktop app

The web browser has stricter memory limits. Open the same database in the Notion desktop app. If the view loads there, clear your browser cache and reload the page. If the error continues in the browser, use the desktop app as your primary access point for that database.

Error occurs after adding a new property to the database

A new formula or rollup property that references many other databases can trigger the error. Delete the new property temporarily. If the view loads, redesign the property to use a simpler calculation or a manual select property instead.

Notion Database View Types: Filtered vs Unfiltered Performance

Item	Filtered View	Unfiltered View
Rows displayed	Only matching rows	All rows
Load time	Longer due to scan	Faster for small databases
Risk of “Cannot Load View”	High with complex filters or large databases	Low
Best use	Databases under 2,000 rows	Any size, but slower for very large sets

You can now fix the “Cannot Load View” error by simplifying filters, duplicating the database, or switching to a linked database view. As a next step, review your database properties and remove any rollup or formula properties that are not essential. For ongoing management, use the Notion desktop app for large databases and archive old rows regularly to keep the database under 5,000 items.