thanks for quick fix

I will watch it and see how the tasks issue goes

Update 2: been about 20 mins and nothing showing up in the task list.

If anyone can confirm that the issue is fixed, that would be great. Thanks.

Edit: Updated to commit 4eeae and also do not experience the task spam. So im guessing this is something that happened during the commits today (Aug 25, 2025)

Edit 2: Tested on both my homelab install and a second test environment install and both seem to exhibit this issue on the latest commit.

marco@xen:/opt/xo/xo-server$ xo-cli rest get tasks/0merqp0hz
404 Not Found
✖ {
  "error": "no such task 0merqp0hz",
  "data": {
    "id": "0merqp0hz",
    "type": "task"
  }
}

OS is Ubuntu 24.04.3 LTS (GNU/Linux 6.8.0-78-generic x86_64)
4 CPU / 4GB Ram
Xen Orchestra, commit c1c3b
Master, commit c1c3b

text when opening up a task- so far they all seem similar with different ids.

{
  "error": "no such task 0merqc0ye",
  "data": {
    "id": "0merqc0ye",
    "type": "task"
  }
}

{
  "error": "no such task 0merqdzm2",
  "data": {
    "id": "0merqdzm2",
    "type": "task"
  }
}

One error in the log

host.getSchedulerGranularity
{
  "host": "4214a8b3-4628-43a6-b10d-c40503dd9694"
}
{
  "code": 1,
  "data": {
    "id": "4214a8b3-4628-43a6-b10d-c40503dd9694",
    "type": "host"
  },
  "message": "no such host 4214a8b3-4628-43a6-b10d-c40503dd9694",
  "name": "XoError",
  "stack": "XoError: no such host 4214a8b3-4628-43a6-b10d-c40503dd9694
    at noSuchObject (/opt/xo/xo-builds/xen-orchestra-202508251601/packages/xo-common/api-errors.js:26:11)
    at Xo.getObject (file:///opt/xo/xo-builds/xen-orchestra-202508251601/packages/xo-server/src/xo.mjs:88:13)
    at file:///opt/xo/xo-builds/xen-orchestra-202508251601/packages/xo-server/src/xo-mixins/api.mjs:172:25
    at /opt/xo/xo-builds/xen-orchestra-202508251601/node_modules/lodash/_createBaseFor.js:17:11
    at baseForOwn (/opt/xo/xo-builds/xen-orchestra-202508251601/node_modules/lodash/_baseForOwn.js:13:20)
    at /opt/xo/xo-builds/xen-orchestra-202508251601/node_modules/lodash/_createBaseEach.js:17:14
    at forEach (/opt/xo/xo-builds/xen-orchestra-202508251601/node_modules/lodash/forEach.js:38:10)
    at Xo.call (file:///opt/xo/xo-builds/xen-orchestra-202508251601/packages/xo-server/src/xo-mixins/api.mjs:163:3)
    at Api.#callApiMethod (file:///opt/xo/xo-builds/xen-orchestra-202508251601/packages/xo-server/src/xo-mixins/api.mjs:411:50)"
}

Seems to be a host that i am testing pcie pass through with. I did redo that host install and used the same name/ip address. Not sure if this is just an error not related to task list issue.

• Deploy a new VM with XO from sources and see if you get the same behavior

• Investigate the XO tasks to see if you can find some commonality

• You can wait to see if others start reporting this same issue

What version of Node is installed on this VM?