Suddenly failing "Invalid input.", "No task status, waiting".

[hbhargava7]

two separate actions-based workflows of mine are suddenly failing. Any leads? I have confirmed all 3 secrets are correct.

Enqueued task [redacted]
No task status, waiting. Task was:
{
  "id": "redacted",
  "eventName": "exportSpace",
  "request": {
    "spaceId": "***",
    "exportOptions": {
      "exportType": "markdown",
      "timeZone": "America/New_York",
      "locale": "en"
    }
  },
  "actor": {
    "table": "notion_user",
    "id": "redacted"
  },
  "rootRequest": {
    "eventName": "exportSpace",
    "requestId": "redacted"
  },
  "headers": {
    "ip": "[13](redacted:6:14).66.79.84",
    "cityFromIp": "San Antonio",
    "countryCodeFromIp": "US",
    "subdivision1FromIp": "US-TX"
  },
  "equeuedAt": [16](redactedstep:6:18),
  "error": "Invalid input.",
  "state": "retryable_failure"
}

Then after a few repeats of that message:

/opt/hostedtoolcache/node/18.18.0/x64/lib/node_modules/notion-backup/node_modules/yauzl/index.js:187
    callback(new Error("end of central directory record signature not found"));
             ^

Error: end of central directory record signature not found
    at /opt/hostedtoolcache/node/18.18.0/x64/lib/node_modules/notion-backup/node_modules/yauzl/index.js:187:14
    at /opt/hostedtoolcache/node/18.18.0/x64/lib/node_modules/notion-backup/node_modules/yauzl/index.js:631:5
    at /opt/hostedtoolcache/node/18.18.0/x64/lib/node_modules/notion-backup/node_modules/fd-slicer/index.js:32:7
    at FSReqCallback.wrapper [as oncomplete] (node:fs:684:5)

Node.js v18.18.0
Error: Process completed with exit code 1.

[den-cezar]

My GitHub action has the same error message, do you have any updates?

[brateq]

I got the same problem, I updated the tokens but no change.

[Yakitrak]

Same here, is there any update on this please?

[darobin]

FWIW I've stopped using Notion (in big part because they don't have a real official API and keep breaking the unofficial one like this) so I'm not in a position to debug this. If people wish to file a PR, I'm happy to review and publish but I won't be providing the patch sorry.

[savemomo]

@hbhargava7 Thank you very much for your help. I have confirmed that this pull request indeed fixes the issue.