Task description constantly saving - loosing content

Hi everyone,
I just installed self-hosted Vikunja on my Synology NAS.
Everything seems to be working just fine.

The only thing which makes it almost unusable is the fact that if you are typing a description to a new item it seems to be constantly saving. This results in very strange behavior if you are typing, deleting, adding text. It then seems to save the changed text, redo parts of text I just added, forget parts, and so on. As soon as I click on the save button all editing steps seems to be repeated and repeated. It is really difficult to describe.

In the test environment here on vikunka.io it is working so it must be related to my installation. Maybe the NAS is simply to slow an cannot keep up with the constant change and saving operations?

I was not able to find anything in the bugs or here in the forum. Has anyone ever experienced something similar?

It sounds like your environment might just be slow.

There are a few issues where this has been discussed:

Thank you, that is exactly what I was looking for. So I guess my NAS is just to slow to cope with the auto-save feature :frowning:

looks like it yes :confused: You can check in the browser’s dev tools network tab whether the update requests really take that long or if it’s something else. Vikunja is relatively lightweight so I doubt your nas is that slow.

I am not that experienced in using the dev tools, however I identified some line items that took 8-30 seconds (!!! not ms) to get responses after e.g. deleting a word in the description.
Even after clicking the save button it does not stop with the saving process even after several minutes and seem to iterate all changes I made in the text field over and over.

At the same time the NAS resource manager states only 30-50% CPU load and about 40% free RAM.
I tried several devices over LAN and WLAN, no difference. All other services on the NAS are accessible.
And for example the Comments text fields in Vikunja work without any problem. And everything else like creating new tasks reacts immediately.

I installed Vikunja following the guide from marius hosting How to Install Vikunja on Your Synology NAS – Marius Hosting

That’s really wired. It should not take that long, especially when the rest is plenty fast?

Anything in the api logs?

The api log does not show any errors as I am aware. The regular access and long duration is visible. Here some of the lines that are produced as soon as I start to edit the description text field:

Blockquote 2023-05-12T13:11:27.002827555Z: WEB :arrow_forward: XX.XX.XXX.XXX POST 200 /api/v1/tasks/4 14.368877902s - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
2023-05-12T13:11:31.154196531Z: WEB :arrow_forward: XX.XX.XXX.XXX POST 200 /api/v1/tasks/4 18.927880384s - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
2023-05-12T13:11:34.211581793Z: WEB :arrow_forward: XX.XX.XXX.XXX OPTIONS 204 /api/v1/notifications?page=1 58.834µs - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
2023-05-12T13:11:34.2699428Z: WEB :arrow_forward: XX.XX.XXX.XXX GET 200 /api/v1/notifications?page=1 20.692888ms - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
2023-05-12T13:11:36.865196655Z: WEB :arrow_forward: XX.XX.XXX.XXX POST 200 /api/v1/tasks/4 13.506849295s - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
2023-05-12T13:11:38.206034599Z: WEB :arrow_forward: XX.XX.XXX.XXX OPTIONS 204 /api/v1/tasks/4 46.12µs - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
2023-05-12T13:11:38.206334308Z: WEB :arrow_forward: XX.XX.XXX.XXX OPTIONS 204 /api/v1/tasks/4 35.729µs - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
2023-05-12T13:11:39.766018298Z: WEB :arrow_forward: XX.XX.XXX.XXX POST 200 /api/v1/tasks/4 11.423796481s - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
2023-05-12T13:11:41.874403134Z: WEB :arrow_forward: XX.XX.XXX.XXX POST 200 /api/v1/tasks/4 18.515872836s - Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36

That looks wired. Are you accessing Vikunja directly or through a proxy / vpn or similar?

I am accessing it directly. I reinstalled it now onm a small NUC and it is working as expected. So it must have to be something with my NAS. Thank you for your support!

1 Like

I have this issue constantly (also on a NAS, but don’t have the means to move Vikunja elsewhere). In the bug reports that were linked earlier, there were mentions of disabling auto-save, but I can’t seem to find how to disable auto-save. Is that a configuration option somewhere? If so, where is it?

I’m not sure how the auto-save currently works, but it feels SUPER aggressive to me. I feel like it should wait longer after you’ve finished typing to initiate the auto-save. It currently initiates auto-saving while I’m actively typing half the time.

Right now it’s not possible to disable auto-save.

I’ve increased the timeout to 5 seconds in f7ba3bd08f.