Error message when in Scheduled Actions

I’m noticing an error whenever I click into the “Scheduled Actions” list.

The “Scheduled Actions” list appears as empty although I have many scheduled actions.

The error pops up saying “Something went wrong”, briefly vanishes and returns after a few seconds.

The error message disappears for good when changing to a different type of action (i.e. “Next”).

I suspect it might have something to do with the fact that I am currently travelling in New Zealand and am 12 hours ahead of my usual timezone (Central Europe).

My computer (Manjaro Linux) is set to the correct timezone. I am using Everdo 1.8.2.

On the Android app, everything functions normally. Old and new “Scheduled Actions” created on the desktop sync flawlessly to my phone.

Here is the output from error.log

{"ts":"2023-02-21T04:13:16.711Z","message":"Invalid offset: 13. Should be between -11 and +12.","stack":"Error: Invalid offset: 13. Should be between -11 and +12.\n at new je (file:///opt/Everdo/resources/app.asar/index.js:540:1000116)\n at je.current (file:///opt/Everdo/resources/app.asar/index.js:540:1000253)\n at Qe.adjustSecondsToCurrentTimezone (file:///opt/Everdo/resources/app.asar/index.js:540:1000597)\n at Ye (file:///opt/Everdo/resources/app.asar/index.js:540:1001482)\n at file:///opt/Everdo/resources/app.asar/index.js:540:1004761\n at file:///opt/Everdo/resources/app.asar/index.js:540:1004677\n at Ge (file:///opt/Everdo/resources/app.asar/index.js:540:1004757)\n at Object.Ze [as NextDate] (file:///opt/Everdo/resources/app.asar/index.js:540:1006616)\n at It (file:///opt/Everdo/resources/app.asar/index.js:540:1009194)\n at Array.sort (<anonymous>)"} {"ts":"2023-02-21T04:13:16.715Z","message":"Invalid offset: 13. Should be between -11 and +12.","stack":"Error: Invalid offset: 13. Should be between -11 and +12.\n at new je (file:///opt/Everdo/resources/app.asar/index.js:540:1000116)\n at je.current (file:///opt/Everdo/resources/app.asar/index.js:540:1000253)\n at Qe.adjustSecondsToCurrentTimezone (file:///opt/Everdo/resources/app.asar/index.js:540:1000597)\n at Ye (file:///opt/Everdo/resources/app.asar/index.js:540:1001482)\n at file:///opt/Everdo/resources/app.asar/index.js:540:1004761\n at file:///opt/Everdo/resources/app.asar/index.js:540:1004677\n at Ge (file:///opt/Everdo/resources/app.asar/index.js:540:1004757)\n at Object.Ze [as NextDate] (file:///opt/Everdo/resources/app.asar/index.js:540:1006616)\n at It (file:///opt/Everdo/resources/app.asar/index.js:540:1009194)\n at Array.sort (<anonymous>)"} {"ts":"2023-02-21T04:13:17.338Z","message":"Invalid offset: 13. Should be between -11 and +12.","stack":"Error: Invalid offset: 13. Should be between -11 and +12.\n at new je (file:///opt/Everdo/resources/app.asar/index.js:540:1000116)\n at je.current (file:///opt/Everdo/resources/app.asar/index.js:540:1000253)\n at Qe.adjustSecondsToCurrentTimezone (file:///opt/Everdo/resources/app.asar/index.js:540:1000597)\n at Ye (file:///opt/Everdo/resources/app.asar/index.js:540:1001482)\n at file:///opt/Everdo/resources/app.asar/index.js:540:1004761\n at file:///opt/Everdo/resources/app.asar/index.js:540:1004677\n at Ge (file:///opt/Everdo/resources/app.asar/index.js:540:1004757)\n at Object.Ze [as NextDate] (file:///opt/Everdo/resources/app.asar/index.js:540:1006616)\n at It (file:///opt/Everdo/resources/app.asar/index.js:540:1009194)\n at Array.sort (<anonymous>)"} {"ts":"2023-02-21T04:14:09.716Z","message":"Invalid offset: 13. Should be between -11 and +12.","stack":"Error: Invalid offset: 13. Should be between -11 and +12.\n at new je (file:///opt/Everdo/resources/app.asar/index.js:540:1000116)\n at je.current (file:///opt/Everdo/resources/app.asar/index.js:540:1000253)\n at Qe.adjustSecondsToCurrentTimezone (file:///opt/Everdo/resources/app.asar/index.js:540:1000597)\n at He (file:///opt/Everdo/resources/app.asar/index.js:540:1003336)\n at Ge (file:///opt/Everdo/resources/app.asar/index.js:540:1004330)\n at o.nextDates (file:///opt/Everdo/resources/app.asar/index.js:540:1517256)\n at ui.get (file:///opt/Everdo/resources/app.asar/index.js:9:26748)\n at ui.evaluate (file:///opt/Everdo/resources/app.asar/index.js:9:27898)\n at o.nextDates (file:///opt/Everdo/resources/app.asar/index.js:9:29757)\n at o.Ja (file:///opt/Everdo/resources/app.asar/index.js:540:1509403)"}

Thank you for providing the log. This issue is being looked at.

It might be a bug with how the timezone is set in the OS, or it might be a bug with one of Everdo’s libraries.

In the meantime, could you please try the following and see if the error goes away?

a) Setting a different time zone with the same GMT offset (my guess is it should be either GMT+12 or GMT-12)
b) Setting your time manually

1 Like

Your hypothesis was correct: Changing the timezone manually to a zone for which the offset is between -11 and +12 resolves the problem.

However, in my system (Manjaro Linux) apparently timezones are defined via UTC offset, which can be larger than 12 for some regions.

One example is the timezone I am currently in: New Zealand (UTC+13).

See the following examples for an brief overview of pacific timezones and if the error occurs:

  • UTC+12 (Norfolk Island): no error :white_check_mark:
  • UTC+13 (New Zealand): error :cross_mark:
  • UTC+14 (Kiribati): error :cross_mark:

UTC+12

UTC+13

UTC+14

Quick update:

I’ve noticed the same behaviour on Windows 10 running Everdo 1.8.5

Reviving this old thread as I am traveling again in the Pacific region and the problem still persists (Windows 10, Everdo 1.9.0).

Unexpected behavior:

  • “An error has occured” message in lower right corner when on any screen with scheduled tasks every 30-40 seconds
  • Unable to switch to “Scheduled tasks” section. Instead, this triggers the “An error has occured” message

Output from error.log:

{"ts":"2025-01-28T06:47:18.617Z","message":"Invalid offset: 13. Should be between -11 and +12.","stack":"Error: Invalid offset: 13. Should be between -11 and +12.\n    at new je (file:///C:/Users/username/AppData/Local/Programs/Everdo/resources/app.asar/index.js:540:1000517)\n    at je.current (file:///C:/Users/username/AppData/Local/Programs/Everdo/resources/app.asar/index.js:540:1000654)\n    at Qe.adjustSecondsToCurrentTimezone (file:///C:/Users/username/AppData/Local/Programs/Everdo/resources/app.asar/index.js:540:1000998)\n    at Ye (file:///C:/Users/username/AppData/Local/Programs/Everdo/resources/app.asar/index.js:540:1001883)\n    at file:///C:/Users/username/AppData/Local/Programs/Everdo/resources/app.asar/index.js:540:1005162\n    at file:///C:/Users/username/AppData/Local/Programs/Everdo/resources/app.asar/index.js:540:1005078\n    at Ge (file:///C:/Users/username/AppData/Local/Programs/Everdo/resources/app.asar/index.js:540:1005158)\n    at Object.Ze [as NextDate] (file:///C:/Users/username/AppData/Local/Programs/Everdo/resources/app.asar/index.js:540:1007017)\n    at It (file:///C:/Users/username/AppData/Local/Programs/Everdo/resources/app.asar/index.js:540:1009595)\n    at Array.sort (<anonymous>)"}

1 Like

Adding to this as I moved to New Zealand this year. This bug makes everdo (1.9.0) almost unusable on Windows in this time zone, because my workflow depends on scheduled recurring actions popping up automatically. Now I have to open everdo on my android phone for this to happen. During winter it was fine because we only had UTC+12, but now that daylight savings started again (UTC+13), the bug is back. Please fix!

1 Like

Thanks for the additional information. A fix is being investigated.

1 Like