Error at the "Run backup" step

Question

Error at the "Run backup" step

Closed this issue 3 years ago · 7 comments

I am recieving this error at the "Run backup" step.

Run notion-backup
  notion-backup
  shell: /usr/bin/bash -e {0}
  env:
    NOTION_TOKEN: ***
    NOTION_SPACE_ID: ***
Enqueued task <enqueued_task>
TypeError: Cannot read property 'pagesExported' of undefined
    at exportFromNotion (/opt/hostedtoolcache/node/12.22.1/x64/lib/node_modules/notion-backup/notion-backup.js:61:51)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at async run (/opt/hostedtoolcache/node/12.22.1/x64/lib/node_modules/notion-backup/notion-backup.js:90:3)
Error: Process completed with exit code 1.

Answer 1 · 2021-07-12T07:59:57.000Z

I tried and found out that removing the quote mark in the TOKEN and SPACE_ID string resolves this problem

Answer 2 · 2021-07-12T12:00:26.000Z

Thanks @Fengyee. Removing the quote marks solved the issue.
I had to run it twice before it could work without error. Not sure if this is related though.

Answer 3 · 2021-12-29T17:52:44.000Z

I don't have quote marks in my secrets for the token and space id. However, the job fails everytime I run it, and I always need to rerun the job manually for it to work. This kind of defeats the purpose of an automatic backup, any ideas?

Answer 4 · 2021-12-29T18:51:27.000Z

What error are you getting?

…

-- Robin Berjon VP Data Governance The New York Times

On December 29, 2021 12:52:57 Davina Zaman ***@***.***> wrote: I don't have quote marks in my secrets for the token and space id. However, the job fails everytime I run it, and I always need to rerun the job manually for it to work. This kind of defeats the purpose of an automatic backup, any ideas? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

Answer 5 · 2021-12-30T03:39:19.000Z

I'm getting the same error as reported above.

Answer 6 · 2022-01-03T17:02:21.000Z

I managed to get the same error once, but then it just disappeared. I think it's a transient problem with how Notion reports the status of open tasks. I have been adding code to handle those cases better in 1.3.0. Let's see if it works. Sorry I can't be more definitive, it's hard to fix this without being able to reproduce it reliably, or even often.

Answer 7 · 2022-01-03T17:31:17.000Z

Gotcha, I understand. It seems to be helpful! After 2 failed scheduled job attempts, it succeeded the other day, I'm assuming after your update. I appreciate it, if I continue to have problems I'll check in in a bit. Happy new year!