[Todoist] 'Menu Bar Tasks' fails in background reload

[kamilmodest]

Extension

https://www.raycast.com/doist/todoist

Raycast Version

1.83.1

macOS Version

14.8

Description

Error:

Error: Item not found

fo:api.ts:82:12

---
79:     const uuid = Object.keys(data.sync_status)[0];
80:     if (data.sync_status[uuid] !== "ok") {
81:       const error = data.sync_status[uuid] as { error: string };
82:       throw new Error(error.error);
83:     }
84:   }
85: 
---

async gi:menu-bar.js:63:6278
async c:menu-bar.js:63:11718

Steps To Reproduce

1. Either log-in via Todoist integration or use a token in the Raycast extension
2. Open Raycast settings (Extensions -> Todoist) and setup Menu Bar Tasks:
   • VIew: Filter
   • Number of Days: 7
   • Filter Query: (Overdue | Today) & (workspace: Work | @💼 WorkTime)
   • Maximum Width: 40
   • Menu Bar Tasks: Activate
   • Background Refresh: on
3. Focus and unfocus one of the today's task via the "Home" menu

Current Behaviour

After initial setup it works, then error appears after background refresh.
When click on 'Reload' button, all tasks appear again and the extension again fails after sometime with error: "Command terminated: Todoist: Menu Bar Tasks".

The error doesn't appear if there's a focused task active

Expected Behaviour

All work resilient :)

[raycastbot]

Thank you for opening this issue!

🔔 @thomaslombart @AnishDe12020 @kud @casassg @Princeyadav05 @jfkisafk you might want to have a look.

💡 Author and Contributors commands

The author and contributors of doist/todoist can trigger bot actions by commenting:

• @raycastbot close this issue Closes the issue.
• @raycastbot close as not planned Closes the issue as not planned.
• @raycastbot rename this issue to "Awesome new title" Renames the issue.
• @raycastbot reopen this issue Reopens the issue.
• @raycastbot assign me Assigns yourself to the issue.
• @raycastbot good first issue Adds the "Good first issue" label to the issue.
• @raycastbot keep this issue open Make sure the issue won't go stale and will be kept open by the bot.

[kamilmodest]

Sometimes it give another error:

AxiosError: Request failed with status code 429

St:settle.js:19:11

---
16:   if (!response.status || !validateStatus || validateStatus(response.status)) {
17:     resolve(response);
18:   } else {
19:     reject(new AxiosError(
20:       'Request failed with status code ' + response.status,
21:       [AxiosError.ERR_BAD_REQUEST, AxiosError.ERR_BAD_RESPONSE][Math.floor(response.status / 100) - 4],
22:       response.config,
---

IncomingMessage.<anonymous>:menu-bar.js:60:8751
IncomingMessage.emit:node:events:531:35
IncomingMessage.emit:node:domain:488:12

I guess the extensions shouldn't fail because of 429 Too Many Requests response code, but gracefully catch it and just to delay requests to the service for some time (and maybe share the warning message with the user)

[raycastbot]

This issue has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 10 days to keep our backlog clean 😊