Error in standard.log when creating a new task -- Task Sync

Bug
1

Bug Report: Tasks Not Indexed Immediately After Creation after recently upgrading to Vikunja (0.24-6)

Environment:

  • Vikunja Frontend: Installed via apt
  • Version: Debian build 0.24-6
  • Deb Package Hash: 4dc42cdd301d3b94d57de85fa817d54125d1b147
  • Platform: Web frontend and mobile client

Issue Description

Newly created tasks are not immediately indexed or accessible to other clients (shared projects, mobile apps) unless a manual index operation (vikunja index) is performed on the CLI. This issue affects both the web frontend and mobile clients, regardless of the originating client.

Reproduction Steps

  1. Create a new task in any folder using the web frontend.
  • Task does not appear in the mobile client.
  • Task is only accessible from the originating web frontend.
  1. Create a new task using a mobile client.
  • Task appears in the web frontend.
  • Task does not appear in the mobile client after creation.
  1. Shared projects are affected similarly—new tasks do not propagate immediately.
  2. Running vikunja index manually resolves the issue, making the tasks accessible.

Observed Errors

Errors in vikunja-standard.log suggest indexing issues related to kanban_position and positions.view_X fields.

2025-02-22T23:04:32-08:00: ERROR :arrow_forward: 3fa0 Errors during index:
[error=Field kanban_position has been declared in the schema, but is not found in the document.,
document={“id”:“368”,“title”:“test for mobile app integration”,“positions”:{“view_105”:98304,“view_106”:98304,“view_107”:98304,“view_108”:98304},“buckets”:[40]}]

2025-02-22T23:05:20-08:00: WARNING :arrow_forward: 4027 Unable to fetch tasks from Typesense,
error was ‘status: 404 response: {“message”: “Could not find a field named positions.view_21 in the schema for sorting.”}’.
Falling back to db.

2025-02-22T23:05:24-08:00: ERROR :arrow_forward: 4073 Errors during index:
[error=Field kanban_position has been declared in the schema, but is not found in the document.,
document={“id”:“369”,“title”:“testing for web page integration”,“positions”:{“view_21”:524288,“view_22”:524288,“view_23”:524288,“view_24”:524288},“buckets”:[10]}]

Manually running vikunja index results in successful indexing:

2025-02-22T23:06:29-08:00: INFO :arrow_forward: 002 Running migrations…
2025-02-22T23:06:29-08:00: INFO :arrow_forward: 06a Ran all migrations successfully.
2025-02-22T23:06:29-08:00: INFO :arrow_forward: 06b Indexing all tasks… This may take a while.
2025-02-22T23:06:30-08:00: INFO :arrow_forward: 5a9 Done!

2

I forgot to mention that, upon a successful index, new tasks began working as expected, I think this occurred when upgrading from 0.24-4 to 0.24-6 however during the installation (and reinstallation) I did a complete reinstall of the platform, restoring my data and encountering the same issue.

One person does not a FAQ make, but in the hopes its indexed somewhere people may be able to find this result quickly from a web search.