> 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/how-to-guides/recalculate-calculated-properties.md).

# Recalculate calculated properties

Use this guide when a formula or rollup is blank, stale, zero, capped, or different from Notion’s UI. Notion still owns the recipe; NotionApps only decides whether a supported recipe should be evaluated from synced data.

### Before you start

1. Share the parent database and every related database with the NotionApps integration.
2. Sync / Reload after adding or changing formulas, rollups, relations, or target fields.
3. Confirm related records have finished syncing.
4. Open Builder → Databases → Calculated properties.

### Read each property

| Label                     | Meaning                                                                |
| ------------------------- | ---------------------------------------------------------------------- |
| Notion recipe             | Read-only definition imported from Notion.                             |
| Status                    | Current supported, Notion-value, waiting, or unsupported state.        |
| Depends on                | Fields and relations required by the recipe.                           |
| Recalculate in NotionApps | On uses supported NotionApps evaluation; off uses Notion’s page value. |

### Enable a supported calculation

1. Select the formula or rollup.
2. Confirm the toggle is clickable.
3. Leave Recalculate in NotionApps on.
4. If the recipe is missing, run Sync / Reload and reopen the panel.
5. Sync every related database.
6. Publish.
7. Allow background processing to complete.
8. Open the published record and verify the result remains stable after reload.

The toggle does not immediately calculate every record in the browser. It enrolls supported fields in asynchronous background processing.

### Supported functions

Formula support includes property references; arithmetic and comparisons; if; and, or, not; empty; now; and dateBetween for days, hours, and minutes. Supported rollups are sum, count, average, min, and max.

The following remain unsupported and use Notion’s value: formatDate, ifs, lets, style, map, filter, join, includes, length, format, and unsupported rollup functions.

### Understand status and delays

| Status                    | Published behavior                                           |
| ------------------------- | ------------------------------------------------------------ |
| We’ll recalculate this    | Work is eligible for background evaluation.                  |
| Using Notion’s value      | Toggle is off; Notion is authoritative.                      |
| Waiting on related fields | Last good value is retained until dependencies are complete. |
| Can’t recalculate         | Toggle is disabled; Notion’s value is used.                  |

Recalculate protects customer-facing sync with queue, latency, and host-load limits. Under pressure, work may be deferred. Duplicate signals are coalesced, terminal unsupported formulas stop recycling, and incomplete dependencies remain isolated until evidence changes. This protects data but means Sync completed does not guarantee the value changed in the same moment.

### Verify correctly

1. Record the current Notion and NotionApps values.
2. Change one source field in a test record.
3. Sync the source and parent databases when needed.
4. Wait for background processing.
5. Reload the published app.
6. Confirm the target formula or rollup changed once and remains stable.
7. Confirm an unrelated record did not change.

### Troubleshooting decision tree

1. Toggle disabled? Read the reason. Unsupported language cannot be fixed by repeated sync.
2. Rollup recipe missing? Share related database and Sync.
3. Waiting on related fields? Confirm relation rows and child database are fully synced.
4. Value uses only 25 rows? Confirm supported rollup, all related rows synced, toggle on.
5. Value still old? Check sync health, publish state, and allow background processing.
6. Value changes then reverts? Confirm Recalculate remains on and field is supported.

### What makers cannot do

Makers cannot manually release internal retries, quarantine rows, override load safeguards, or force unsupported expressions to evaluate. Contact support with the app, database, property, example record, expected value, and actual value when supported work remains stale.

### Related

* [Formulas & Rollups](https://docs.notionapps.com/screens-and-components/formulas-and-rollups)
* [Reload and sync](https://docs.notionapps.com/databases/reload-and-sync)
* [9 Oct 2026 Release](https://docs.notionapps.com/release-notes/9-oct-2026-release)


---

# 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/how-to-guides/recalculate-calculated-properties.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.