Why am I getting console errors when trying to connect Todoist and Habitify in my automation?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi! Would love some support. My automation connects Todoist and Habitify. I’m getting the following console errors:

This:


Log
[debug] err.response {
  "status": 410,
  "statusText": "Gone",
  "headers": {
    "content-type": "text/plain; charset=utf-8",
    "transfer-encoding": "chunked",
    "connection": "keep-alive",
    "date": "Wed, 18 Feb 2026 19:59:23 GMT",
    "vary": "Accept-Encoding",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
    "x-cache": "Error from cloudfront",
    "via": "1.1 [a41d734044cac7cfe09820f04854befc.cloudfront.net](http://a41d734044cac7cfe09820f04854befc.cloudfront.net) (CloudFront)",
    "x-amz-cf-pop": "IAD61-P10",
    "alt-svc": "h3=\":443\"; ma=86400",
    "x-amz-cf-id": "NYg8d2rmAdtg7hp8nGC6pnpZEBiW4cKqENUkRoyv9DASnJKrV1iwjA=="
  },
  "config": {
    "transitional": {
      "silentJSONParsing": true,
      "forcedJSONParsing": true,
      "clarifyTimeoutError": false
    },
    "adapter": [
      "xhr",
      "http",
      "fetch"
    ],
    "transformRequest": [
      null
    ],
    "transformResponse": [
      null
    ],
    "timeout": 0,
    "xsrfCookieName": "XSRF-TOKEN",
    "xsrfHeaderName": "X-XSRF-TOKEN",
    "maxContentLength": -1,
    "maxBodyLength": -1,
    "env": {},
    "headers": {
      "Accept": "application/json, text/plain, **/**",
      "Content-Type": "application/x-www-form-urlencoded",
      "Authorization": "Bearer ce7933eabe81a0d5c7b15e428224184451425a67",
      "User-Agent": "axios/1.9.0",
      "Content-Length": "101",
      "Accept-Encoding": "gzip, compress, deflate, br"
    },
    "method": "post",
    "url": "https://api.todoist.com/sync/v9/completed/get_all",
    "data": "annotate_items=true&since=2026-02-10T23%3A59%3A15.992Z&token=ce7933eabe81a0d5c7b15e428224184451425a67",
    "allowAbsoluteUrls": true
  },
  "data": "This endpoint is deprecated.\n\nIf you're reading this on a browser, there's a good chance you can change\nthe v8 part on the URL to v1 and get away with it. ;)\n\nIf you're using the API directly, please update your use case to rely\non the new API endpoints, available und

and

error
AxiosError: Request failed with status code 410
at settle (/pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/node_modules/.pnpm/axios@1.9.0/node_modules/axios/lib/core/settle.js:19:12)
at Unzip.handleStreamEnd (/pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/node_modules/.pnpm/axios@1.9.0/node_modules/axios/lib/adapters/http.js:599:11)
at Unzip.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
at Axios.request (/pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/node_modules/.pnpm/axios@1.9.0/node_modules/axios/lib/core/Axios.js:45:41)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async callAxios (/pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/node_modules/.pnpm/@pipedream+platform@3.0.3/node_modules/@pipedream/platform/dist/axios.js:110:26)
at async Object.getCompletedTasks (file:///pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/code/todoist.app.mjs:776:15)
at async Object.getSyncResult (file:///pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/code/sources/completed-task/completed-task.mjs:21:21)
at async Object.run (file:///pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/code/sources/common.mjs:53:24)
at async /var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:105:11
at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)
at async deployedComponentMain (/var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:44:20)
at async MessagePort.<anonymous> (file:///var/task/component_maker.mjs:181:9)

This started happening without any prompting. It was working fine a couple weeks ago.

Thank you!

2

Hi, are you running actions from the public registry or custom code? If you’re using actions, can you tell me which ones?

3

Doing a mix of Todoist’s completed-task and Habitify node code.

Screenshot 2026-03-09 at 19.42.40.png
Screenshot 2026-03-09 at 19.42.40.png682×696 39.8 KB

4
5

Thanks! Our team will look into it.

6

Posted thread to Discourse: Why am I receiving 410 status code and console errors when connecting Todoist and Habitify through automated script?

7

Any luck with this?

8

Apologies, we looked into it but I missed getting back to you. Can you confirm if you’re running the latest version of the Todoist component? (if you enter edit mode in your workflow, you might see an ‘update’ button on it)

9

We recently updated the Todoist integration to use the latest v1 API. The endpoint called you in the error you shared is still the old one from the v9 API, which is no longer used in the latest version of the Todoist components

10

Thank you! I asked the AI agent to help upgrade it because I couldn’t see a button to do it. It told me it did update the components. I went ahead and tested but it still doesn’t work. When I check the logs I get the same message as before:

AxiosError: Request failed with status code 410
at settle (/pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/node_modules/.pnpm/axios@1.9.0/node_modules/axios/lib/core/settle.js:19:12)
at Unzip.handleStreamEnd (/pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/node_modules/.pnpm/axios@1.9.0/node_modules/axios/lib/adapters/http.js:599:11)
at Unzip.emit (node:events:531:35)
at endReadableNT (node:internal/streams/readable:1696:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
at Axios.request (/pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/node_modules/.pnpm/axios@1.9.0/node_modules/axios/lib/core/Axios.js:45:41)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async callAxios (/pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/node_modules/.pnpm/@pipedream+platform@3.0.3/node_modules/@pipedream/platform/dist/axios.js:110:26)
at async Object.getCompletedTasks (file:///pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/code/todoist.app.mjs:776:15)
at async Object.getSyncResult (file:///pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/code/sources/completed-task/completed-task.mjs:21:21)
at async Object.run (file:///pipedream/dist/code/f5d79ce0ef1656f952e9fce643d88b1ab3787434138c1bf90b53f3bda80d35fd/code/sources/common.mjs:53:24)
at async /var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:105:11
at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)
at async deployedComponentMain (/var/task/node_modules/@lambda-v2/component-runtime/src/deployedComponentMain.js:44:20)
at async MessagePort.<anonymous> (file:///var/task/component_maker.mjs:181:9)
11

Maybe the endpoint is being called in one of the code steps of the workflow?

12

I’m not sure what you mean by that

13

I meant one of your code steps in the workflow could be calling the outdated endpoint. They seem to be different apps though, so it’s more likely that the trigger still isn’t up-to-date with the latest one from the registry. You should click on “Edit” when inspecting the workflow to confirm if there’s an update button on the trigger when you enter edit mode.

14

I’m not sure if the agent can actually update components in an existing workflow, assuming you mean our String agent.