splitbee/notion-api-worker

Page Threw Exception Error 1101

shyrz opened this issue · 9 comments

shyrz commented

My pageId is be69a36ae0a447bc8c3d36a803be48da, and it threw exception error 1101.
The subpage in it works well.

shyrz commented

After 10mins it works... but threw the same error mins later

shyrz commented

image

dvdsgl commented

I'm getting the same with https://notion-api.splitbee.io/v1/table/015fe5ac66da487a934b9aacc2ef9dea

I tried master locally and it worked, but deployed master failed when deployed.

shyrz commented

In wrangler dev, the true error is:

Uncaught (in promise)
TypeError: Cannot read property 'value' of undefined
    at Object.t.getCollectionData (worker.js:1:4367)
    at Object.t.pageRoute [as handler] (worker.js:21:5735)
    at async c (worker.js:1:6415)
Uncaught (in response)
TypeError: Cannot read property 'value' of undefined
dvdsgl commented

I avoided the bug by removing the Person column in my table.

viktorfa commented

I fixed this by replacing limit: 999 with limit: 30 on line 19 in src/api/notion.ts.

const loadPageChunkBody = {
  limit: 30,
  cursor: { stack: [] },
  chunkNumber: 0,
  verticalColumns: false,
};

Maybe Notion is experimenting with rate limits and blocking requests with too high limit?

tobiaslins commented

@zhigang1992 we started blocking specific pages/requests due non fair use limits. You send over 2 million requests to that table in the last month.
Feel free to self host this worker in that case (or drastically reduce requests send to us)

  • 👍1
  • 😄2
  • ❤️1
  • 👀1
zhigang1992 commented

@tobiaslins

Wow, we are terribly sorry, we were under the wrong impression that it will cache on the browser end.

So we just kept calling fetch. 🤦

We'd like to pay for that cost, please let us know how. My email is zhigang1992@gmail.com