Fix Notion Rollup Cannot Calculate Empty Aggregation: Default Workaround

You see the error “Cannot calculate aggregation” when a Notion rollup property tries to aggregate values from an empty set of related database items. This happens because Notion rollups require at least one related record to perform functions like sum, average, or count. This article explains why the error occurs and provides a default workaround using a helper formula and a fallback database entry.

Why a Notion Rollup Shows “Cannot Calculate Aggregation”

A Notion rollup property reads values from a related database through a relation property. When the relation has no linked items, the rollup has zero values to aggregate. Aggregation functions such as Sum, Average, Count All, Min, and Max require at least one data point. If the rollup receives an empty set, Notion cannot perform the math and displays the error text in the cell.

This is not a bug. It is the expected behavior of the aggregation engine. The workaround must guarantee that the rollup always receives at least one numeric value, even if that value comes from a placeholder record.

The Role of the Relation Property

The relation property is the bridge between two databases. You can configure it to show or hide empty relations. By default, if you disable the “Show Empty” toggle in the relation property settings, a rollup that depends on that relation will see zero linked items. The rollup then has no input, and the aggregation fails.

Steps to Build the Default Workaround

This workaround uses a helper database with one fallback entry. The fallback entry provides a default value (0) that the rollup can aggregate. A formula on the source database displays 0 when no real related items exist, and the real rollup value when items are present.

1. Create the helper database
   Add a new database in your Notion workspace. Name it “Rollup Helpers.” Inside it, add one single property: a Number property named “Default Value.” Create exactly one page in this database. Set the “Default Value” to 0.
2. Add a relation to the helper database
   In your original source database (the one that contains the faulty rollup), add a new Relation property. Connect it to the “Rollup Helpers” database. Name this relation “Helper Relation.”
3. Link every source page to the fallback item
   Open each existing page in your source database. In the “Helper Relation” property, select the single fallback page from the “Rollup Helpers” database. For new pages, add this link as part of your creation workflow.
4. Create the fallback rollup
   In the source database, add a new Rollup property. Name it “Fallback Rollup.” Set it to use the “Helper Relation” as the relation. Select the “Default Value” property from the helper database. Set the aggregation to “Sum.” This rollup will always return 0 because the helper page’s value is 0.
5. Create the real rollup
   Add another Rollup property. Name it “Real Rollup.” This is the rollup you originally wanted — the one that aggregates values from your main related database. If you already have this rollup, rename it to “Real Rollup” for clarity.
6. Build the display formula
   Add a Formula property to the source database. Name it “Display Rollup.” Enter this formula:

   if(empty(prop("Real Rollup")), prop("Fallback Rollup"), prop("Real Rollup"))

   This formula checks whether the real rollup is empty. If it is empty, the formula shows 0 (from the fallback). If the real rollup has a value, it shows that value.

7. Hide the helper properties
   Right-click the column headers for “Helper Relation,” “Fallback Rollup,” and “Real Rollup.” Select “Hide” on each. Only the “Display Rollup” formula column remains visible.

If Notion Still Shows the Error After the Workaround

Rollup still shows “Cannot calculate aggregation”

Verify that every source database page has the fallback page linked in the “Helper Relation” property. If even one page lacks the link, the rollup on that page will still fail. Use a database view grouped by the helper relation to find pages with no link.

Formula returns an empty string instead of 0

The empty() function in Notion treats a rollup that returns an error as empty. If the formula shows nothing, check that the fallback rollup property name matches exactly what you wrote in the formula. Also confirm that the helper database page has a numeric value, not a blank cell.

New pages break the workaround

When you create a new page in the source database, you must manually link it to the fallback page in the “Rollup Helpers” database. To automate this, create a template in the source database that includes the helper relation already linked to the fallback page. Apply the template to every new page.

Workaround Methods Compared

Item	Helper Database + Formula	Manual Zero Entry
Setup time	10 minutes	2 minutes per page
Scalability	Works for hundreds of pages	Impractical beyond a few pages
Automation	Uses templates and formulas	Requires manual data entry
Error prevention	Eliminates “Cannot calculate aggregation” entirely	Only works if every page has a manual zero

The helper database method is the recommended workaround because it requires a one-time setup and scales without additional effort. The manual zero entry method is not a viable solution for databases with more than a handful of pages.

You now have a repeatable workaround that prevents the rollup aggregation error in Notion. Apply the helper database and formula to any source database that suffers from this issue. For an even cleaner setup, use the formula to display a custom message like “No data” instead of 0. This approach also works with Count, Average, Min, and Max aggregations by adjusting the fallback value accordingly.