Fix Notion Sync Stuck on Specific Database View After Refresh

When you refresh a Notion page that contains a database view, the sync process may hang indefinitely, showing a spinning loader or a blank screen. This typically occurs because the database view has a corrupted filter, a broken relation, or a formula that references a deleted property. The problem is isolated to that specific view, not the entire workspace. This article explains the root cause and provides step-by-step fixes to restore the view without losing your data.

You will learn how to identify the corrupt element, remove it safely, and rebuild the view. The fixes require only a few minutes and do not affect other database views or pages.

Why a Specific Database View Gets Stuck After Refresh

Notion stores the configuration of each database view as a set of parameters: filters, sorts, grouped properties, and formulas. When you refresh the page, Notion re-evaluates these parameters. If a parameter references a property that no longer exists, or if a filter value is malformed, the re-evaluation loop fails to complete. The database engine attempts to resolve the reference but cannot, causing the sync to hang indefinitely.

Common triggers include renaming a property that is used in a filter, deleting a related database that supplies a rollup, or editing a formula that contains an invalid function call. The problem is view-specific because only that view’s parameters contain the broken reference.

Corrupt Filter Conditions

A filter that uses a property that was deleted or renamed after the filter was created will cause the view to fail on refresh. For example, a filter that checks “Status equals Done” will break if the Status property is renamed to “State.” The filter still points to the old property ID, which no longer exists.

Broken Relation or Rollup

A relation column that links to a database that has been removed, or a rollup that depends on a deleted property in the linked database, will block the view from rendering. Notion tries to fetch the related data but receives no response, leaving the sync stuck.

Formula Errors

Formulas that reference properties by name will break if the referenced property is renamed or deleted. The formula engine throws an error that the view cannot handle gracefully, resulting in a hung refresh.

Steps to Unstick the Database View

Follow these steps in order. Stop after each step and refresh the page to see if the view loads. If the view loads, you do not need to continue to later steps.

1. Duplicate the view
   Open the stuck database view. Click the view name at the top of the database. Select Layout > Duplicate view. Name the duplicate something temporary like “Test View.” Refresh the page. If the duplicate loads, the original view had a corrupt parameter. Delete the original view and use the duplicate.
2. Clear all filters
   If duplicating did not work, click the view name and select Filter. Click Clear all filters. Refresh the page. If the view loads, one of the old filters was corrupt. Reapply filters one at a time, testing after each addition, to identify the broken filter.
3. Remove all sorts
   Click the view name and select Sort. Click Clear all sorts. Refresh the page. A corrupt sort condition can also cause a hang.
4. Remove formula properties
   Click the view name and select Properties. Look for any property of type Formula. Click the formula property and choose Remove property. Refresh the page. If the view loads, the formula had an invalid reference. Recreate the formula with the correct property names.
5. Remove relation and rollup properties
   In the Properties menu, remove any Relation or Rollup properties one at a time, refreshing after each removal. When the view loads, the last removed property was the cause. Recreate the relation or rollup with the correct linked database.
6. Create a new view from scratch
   If none of the above works, click the view name and select Layout > Add a view. Choose the same view type (Table, Board, Calendar, etc.) and name it. Do not copy the original view’s settings. Configure filters, sorts, and properties manually. Delete the old, stuck view.

If Notion Still Has Issues After the Main Fix

Other views on the same database are also stuck

If more than one view is stuck, the problem is likely in the database itself, not a view. Check for a corrupt property that is used by multiple views. Remove properties one at a time from the database schema until the views load.

The entire workspace sync is stuck

If the whole workspace fails to load, the issue is not view-specific. Try logging out and logging back in, or clearing your browser cache. For desktop app, go to Settings & Members > Troubleshooting > Clear cache.

The view loads but data is missing

If the view loads after clearing filters but some rows are missing, the filter that was removed was hiding those rows. Reapply the filter carefully, ensuring the filter value matches an existing property value exactly.

Item	Original view (stuck)	Duplicate view (working)
Filters	May contain broken reference	Empty (no filters applied)
Sorts	May contain broken reference	Empty
Properties	May contain corrupt formula or relation	Same as database default
Layout	Same as duplicate	Same as original
Sync status	Stuck on refresh	Loads normally

After you identify and remove the corrupt element, you can restore the view’s filters, sorts, and properties one at a time. Always test after each addition by refreshing the page. This method prevents the sync from getting stuck again.

You can now fix a Notion database view that hangs after refresh by duplicating the view or clearing its filters. Next time you change a property name, check all views that use that property in filters, formulas, or relations. For advanced prevention, use the Layout > Duplicate view feature before editing any database property to preserve a working backup.