> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/troubleshooting/why-are-my-rollups-on-notionapps-showing-zero-0-value-or-an-incorrect-value.md).

# Why are my rollups on NotionApps showing zero (0) value or an incorrect value?

Start with Builder → Databases → Calculated properties. A zero or incorrect rollup usually comes from one of four conditions: Notion returned an incomplete leaf, a related database is missing, the recipe is unsupported, or background recalculation is waiting on complete dependencies.

### Step 1 — Check the toggle and status

1. Open the affected property.
2. Confirm Recalculate in NotionApps is on and clickable.
3. Read Status and Depends on.
4. If the switch is disabled, read the reason instead of repeatedly toggling or syncing.

Supported rollups are sum, count, average, min, and max. Unsupported formula tokens and rollup functions continue to use Notion’s value.

### Step 2 — Share and sync every database

1. List every relation used by the rollup or formula.
2. Share each related database with the NotionApps integration.
3. Sync the child databases first.
4. Sync the parent database.
5. Reopen Calculated properties and confirm the recipe is loaded.

A parent can remain Waiting on related fields until the child sheet and relation evidence are complete. NotionApps keeps the last good value rather than inventing a result from partial data.

### Step 3 — Understand the 25-related-page issue

Notion’s page API may return only part of a large relation, causing zero, 25, or another incomplete result. When a supported rollup is on, NotionApps computes from the related records it has synced. That only works when all related databases and rows are available.

You no longer need to rebuild supported sum/count/average/min/max rollups as map/length formulas. Those formula tokens are themselves unsupported by the NotionApps evaluator.

### Step 4 — Test one record

1. Choose a non-critical parent record.
2. Note the current target value.
3. Change one related source value.
4. Sync when required.
5. Wait for asynchronous recalculation.
6. Reload the published app.
7. Confirm the expected value and verify it does not revert.

### If the value still does not move

| Observation                        | Likely cause                            | Action                                                             |
| ---------------------------------- | --------------------------------------- | ------------------------------------------------------------------ |
| Toggle disabled                    | Unsupported recipe                      | Use Notion’s value or simplify the recipe in Notion.               |
| Recipe missing                     | Related schema not loaded               | Share and sync databases.                                          |
| Waiting on related fields          | Relation/child sync incomplete          | Finish sync; do not force a partial value.                         |
| Toggle on, supported, but stale    | Background work deferred or blocked     | Confirm Sync Health, then contact support with exact IDs/examples. |
| Value changes then returns to zero | Wrong value source or unsupported field | Confirm toggle/status and republish.                               |

### Information to send support

* App name or ID
* Parent database and property name
* Related database and relation property
* Example record
* Expected and actual values
* Whether Recalculate is on/clickable
* Current status/reason
* Time of last source change and sync

### Related

* [Recalculate calculated properties](https://docs.notionapps.com/how-to-guides/recalculate-calculated-properties)
* [Formulas & Rollups](https://docs.notionapps.com/screens-and-components/formulas-and-rollups)
* [Reload and sync](https://docs.notionapps.com/databases/reload-and-sync)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.notionapps.com/troubleshooting/why-are-my-rollups-on-notionapps-showing-zero-0-value-or-an-incorrect-value.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.