You are viewing a Notion database rollup property and the cell displays the word “Calculating” instead of the expected number, date, or text value. This usually means the rollup engine cannot finish processing the formula because of a circular reference, a broken relation, or an excessively large dataset. In this article, you will learn why the rollup gets stuck, how to fix the underlying cause, and what to do when the problem persists.
Key Takeaways: Fixing a Stuck Notion Rollup Calculation
- Database Relations > Edit Property > Remove circular reference: Break any loop where Database A rolls up a value from Database B, which rolls up a value from Database A.
- Rollup > Edit Property > Change aggregate function: Switch from “Show original” to “Sum” or “Count” to reduce complexity when the rollup involves many linked rows.
- Database > Duplicate view > Delete original rows: Create a fresh copy of the database to clear corrupted relation metadata that blocks the calculation engine.
Why a Notion Rollup Shows “Calculating” Instead of a Value
A rollup property pulls data from a related database by following a relation link and applying an aggregate function such as Sum, Average, Count, or Show original. The calculation engine runs in the background and updates the rollup value whenever the source data changes. When the engine cannot finish, it leaves the cell in a “Calculating” state.
The most common technical root cause is a circular reference. This happens when Database A has a relation to Database B, and Database B has a relation back to Database A, and at least one rollup in the chain references the other database. The engine enters an infinite loop because each update triggers another update on the opposite side.
A second cause is an excessive number of linked rows. If a single rollup must aggregate data from hundreds or thousands of related records, the engine may time out before finishing. This is especially common with the “Show original” function, which tries to display every linked value as a comma-separated list.
A third cause is corrupted relation metadata. When you delete a relation column or rename a linked database, the rollup property can lose its reference point. The engine sees a broken link and cannot proceed with the calculation.
Steps to Unstick a Rollup That Shows “Calculating”
- Identify the circular reference
Open the database that contains the stuck rollup. Click the database name in the top-left corner, then select “Properties.” Look at the Relation property linked to the rollup. Now open the related database and check if it has a Relation property pointing back to the first database. If yes, and if either database uses a rollup that references the other, you have a circular reference. - Remove the circular reference
Decide which rollup is not essential. Open the rollup property settings by clicking the property name in the database view, then select “Edit property.” Change the “Relation” field to a different relation that does not create a loop. If no alternative relation exists, delete the rollup property entirely and recreate it using only a one-way relation. - Reduce the number of linked rows
If the rollup must aggregate many rows, change the aggregate function. Click the rollup property name, select “Edit property,” and in the “Calculate” dropdown choose “Sum” or “Count” instead of “Show original.” Sum and Count require less memory and finish faster. If you need the original values, consider using a linked database view instead of a rollup. - Duplicate the database to clear corrupted metadata
Hover over the database name in the sidebar, click the arrow next to the name, and select “Duplicate.” Give the duplicate a new name. Open the duplicate and check if the rollup now displays a value. If it does, delete the original database and rename the duplicate to the original name. This removes any hidden corruption in the relation metadata. - Recreate the rollup from scratch
If the duplicate method does not work, delete the problematic rollup property. Click the property name, select “Delete property.” Create a new rollup by clicking “+ Add a property,” choosing “Rollup,” and selecting the correct Relation and source property. Use a simple aggregate function such as Count first, then change it to your desired function after the value appears. - Refresh the page and wait
After making changes, press F5 or Ctrl+R to refresh the browser. Notion recalculates rollups in the background. Give the engine up to 30 seconds to finish. If you use the desktop app, close and reopen it.
If the Rollup Still Shows “Calculating” After the Main Fix
Rollup references a formula that depends on the same rollup
A formula property can reference a rollup, and that rollup can reference a property that the formula updates. This creates a dependency loop. Open the formula property and check if it includes the rollup name in its expression. Remove that reference or replace it with a direct relation property. The rollup will calculate immediately after the loop is broken.
Database contains too many properties
Notion databases with more than 50 properties can slow down rollup calculations. Delete unused properties by clicking the property name and selecting “Delete property.” Focus on removing formula properties, rollup properties, and relation properties that are not actively used. Fewer properties mean less work for the rollup engine.
Rollup uses “Show original” with more than 100 linked rows
The “Show original” function tries to display every value from every linked row. When the number of linked rows exceeds 100, the engine often fails to finish. Change the aggregate function to “Count” or “Sum” as described in step 3 of the main fix. If you must see the original values, use a linked database view filtered to show only the relevant rows.
Notion Rollup States: Calculating vs Stale vs Empty
| State | What It Means | What the User Sees |
|---|---|---|
| Calculating | The engine is actively processing the rollup but cannot finish due to a loop, timeout, or broken reference | Gray text “Calculating” in the cell |
| Stale | The rollup value was calculated in the past but the source data changed and the engine has not re-run yet | Previous value with a yellow warning icon |
| Empty | No related rows exist, or the relation property has no linked records | Blank cell or dash |
Understanding these states helps you decide which fix to apply. A “Calculating” indicator always requires one of the fixes above. A stale value usually resolves after a manual page refresh. An empty cell means you need to add linked records to the relation.
You can now identify and remove circular references, reduce rollup complexity, and clear corrupted metadata to make your Notion rollup display the correct value. After applying the fix, test the rollup by adding a new row to the source database and checking that the rollup updates within a few seconds. For databases with frequent updates, use “Sum” or “Count” instead of “Show original” to keep calculations fast and avoid future “Calculating” states.