Using the Notion API with OAuth2 in Google App Script, my computed rollup sums differ from Notion’s display. Could this be due to API limitations or a configuration issue?
I have encountered a similar situation when working with computed fields using Notion’s API. My approach has been to verify that the values and data types coming from the API match what I expect in my code. I’ve noticed that certain rounding behaviors or implicit type conversions can cause minor discrepancies, and these can be attributed to how the API processes rollup aggregations internally. Adjusting my code to handle potential type mismatches or rounding issues often resolves the discrepancy. It may also help to cache values temporarily for a double-check before trusting the final computed result.
In my experience, discrepancies in Notion API rollup values often stem from issues in synchronization and numeric processing rather than explicit bugs. I’ve observed that minor formatting differences can lead your code to misinterpret the aggregated values if the data types are not precisely managed. It is important to cross-check that both the displayed values and the API responses represent numbers in the same format and that any rounding implementation is consistent. A thorough review of your conversion routines and a brief testing phase typically reveal if this is due to misconfiguration or an underlying issue with how the API computes its values.
i’ve seen similar issues, seems like a data conversion or rounding quirk more than a pure bug. might be worth checking type formats and minor sync delays
Over the past few months I encountered similar discrepancies with Notion API rollup values. My personal experience shows that timing issues between rapid updates and the API’s refresh rate often lead to slight mismatches compared to what Notion displays. I resolved this by ensuring that my code accounted for potential caching delays and by enforcing uniform conversion protocols in my calculations. Adjusting the interval between data updates and verifying data types at every step proved beneficial. While it may not be an outright bug in Notion, careful management of synchronization and conversions is usually necessary to achieve the expected results.