Annotation: Server error, couldn't save annotation fields.

[brusboks]

In Explore and Annotate, when I follow the instructions on adding an annotation field and choose "update fields," I get the error "Server error, couldn't save annotation fields."

I have updated to v. 1.52, installed on a local server accessible through our local network. Installed following the Docker instructions. I have just set it up and have been testing to see if everything works, but this error was unexpected. Is this something that is known? Do I need to configure something?

Thanks!

[sal-uva]

Hi there, thanks for the heads up! That should indeed not happen. Can you let me know a bit more about the exact steps you made to produce this error? Is there a log error in Control Panel -> View logs that can tell us more?

[brusboks]

Hi Sal!

I am sorry for never following this up. I've had a crazy spring, and I feel so bad that you were so quick to respond and I completely ghosted here. I wanted to follow up now. I have upgraded to 1.54, everything is running nicely except still annotation - recieving the same error. in the terminal it registers that I click "apply" in the form of something being sent (POST), and then no more.

There is no trace of it in the "view logs" in the interface, however the debug log is not there, only backend and frontend.
After updatering and running, the last logged in backend is this:
03-06-2026 14:11:40 | INFO at manager.py:73: 4CAT Started
03-06-2026 14:11:40 | INFO at manager.py:150: Starting new worker for job api/localhost
03-06-2026 14:11:40 | INFO at api.py:79: Local API listening for requests at backend:4444

I have been trying to problem solve with my colleague who is more adapt than me, but we are a bit stumped as to why this is happening. Any advice is much appreciated, otherwise we will also continue looking into this next week :)

[sal-uva]

All good Camilla! I can't replicate this yet so will need some more information:

• Is it possible to link to the dataset page / dataset (can also be via email)? Knowing what the data source and dataset look like can help me identify the issue.
• What kind of annotations are you making?

[marionwalton]

Hi Sal, I am getting the same error on any dataset I try to annotate, with all kinds of annotations: Server error, couldn't save annotation fields

Server is at http4cat.uct.ac.za and was recently updated to v1.54

Will link you to the dataset via email

[brusboks]

Our 4CAT is only accessible through our university network, so I can't share a workable link with you unfortunately.
I did a test-dataset, collecting from bluesky through 4CAT, and then doing a test-annotation choosing to add text field. See image below.

I did another test-dataset using Zeeschuimer, collected from tiktok, and import to 4CAT. then tried doing the same annotation as above. Same thing.

Should I send you the .csv-files by e-mail ?

[sal-uva]

Hi Camilla, thanks for the info. Without more details on what happens on your server I can't figure out exactly what's happening and I still can't reproduce this.. I suspect it has something to do with erroneous migration.

Can you share the browser console output and what the HTTP response is when you try to save the fields? Open the dev tab (F12), check the console and then the network tab and see what comes in when you click 'Apply'.

@marionwalton if you could also share this, that'd be great :)

[dale-wahl]

I would like to note that you should be able to see something in the frontend logs. The Control Panel -> View logs has a Frontend Logs section. You should be able to recreate your bug and then refresh that page and see something that might help us identify the cause.

The only way I have found to recreate the error you are seeing that we are aware of is to try to create/update annotations for a DataSet that was deleted.

It may be that your 4CAT administrator needs to follow the upgrade instructions for Docker specifically if the interactive upgrade was not successful.

[brusboks]

Thank you so much both if you, I will either follow up tomorrow or next week (so much going on now). I will share browser console output and HTTP response.

I upgraded following the docker upgrade instructions.