Notion Rollup Not Calculating Correctly? Here’s What Fixes It
Table of Contents
Why Rollups Show the Wrong Number
A rollup in Notion is only as reliable as the relation and property it’s pulling from. The single biggest cause of “wrong” rollup values is a mismatch between the rollup’s calculation type and the actual data — for example, a rollup set to “Show original” or “Count all” instead of “Sum,” which will display something technically correct but not the number you expected.
The second common cause is a broken or partially removed relation. If someone deletes a linked page, unlinks a relation, or a page gets moved to a different database entirely, the rollup can silently exclude that value from its calculation without any visible warning.
Filters are the third culprit. If your rollup property has a filter applied (even one you forgot about), it will only calculate based on the filtered subset, not every linked item — which is exactly what happened in my case.
How to Fix It
- Open the rollup property settings. Click the property header, then “Edit property,” and check the “Calculate” dropdown — make sure it’s actually set to Sum, Average, or whatever you intend, not just “Show original.”
- Check for a hidden filter. Within the rollup settings, look for a “Filter” section. If one is applied, review exactly what it’s including or excluding.
- Verify every relation is still intact. Open a few of the linked pages directly and confirm the relation property still points back to the correct database entry.
- Check the source property’s data type. If you’re rolling up a number field, confirm every linked page actually has a number in that field — a single blank or text value can sometimes throw off the calculation depending on the rollup type.
- Refresh the page. Notion occasionally needs a manual refresh (or reopening the database) to recalculate a rollup after a bulk edit.
How I Prevent This Now
I now label my rollup properties clearly (like “Total Spend (Sum)”) so the intended calculation is obvious at a glance, and I do a monthly spot-check comparing the rollup total against a manual count on smaller databases. It takes two minutes and has caught this exact issue twice since.
I also try to avoid stacking filters directly on a rollup property when a simpler linked database view with its own filter would do the same job more transparently — it’s easier to spot a filter on a full view than one buried inside a single property’s settings.
Conclusion
A rollup showing an unexpected number is almost never a Notion bug — it’s usually a filter, a calculation type, or a broken relation quietly changing what’s actually being counted. Checking those three things in order will find the cause nearly every time.
Frequently Asked Questions
Can a rollup include values from multiple relation properties?
No, a single rollup property can only pull from one relation at a time. To combine multiple relations, you’d need separate rollup properties and a formula to combine them.
Why does my rollup show ‘Calculate’ with no visible number?
This usually means the calculation type is set to something like ‘Show original,’ which displays the raw linked values instead of a computed number.
Does archiving a linked page affect the rollup?
Yes, archived pages are typically excluded from rollup calculations even though the relation technically still exists, which can cause totals to drop unexpectedly.