-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Many blocks are missing from page response #41
Comments
Hmmm, comparing https://www.notion.so/Copy-of-2020-Q4-bc7f910ef23b421487ca21b959c67c49 with https://react-notion-x-demo.transitivebullsh.it/bc7f910ef23b421487ca21b959c67c49, I'm not able to see any difference for the part of the document in question. Have you tried using https://github.com/NotionX/react-notion-x? See attached screenshot. |
This probably has to do with In particular, I think |
Wow! NotionX looks awesome! Trying now 👍 |
I confirmed that |
Hello, any update on this? |
After a recent update, many blocks are no longer returned for our pages. One page dropped 50-100 blocks from the end of the page.
In page bc7f910ef23b421487ca21b959c67c49, block
771f85de-f188-46e6-90d6-9b2dd814ba10
is listed in the content of the page, but the block content is not actually included.We noticed that by deleting early blocks on the actual Notion page, missing blocks can be fetched by the API — in other words, blocks at the end of the page are more likely to be missing.
The text was updated successfully, but these errors were encountered: