My deleted attribute is “stuck”

I tried to delete an attribute from a collection, and it’s entered some kind of limbo state called “stuck”. Restarting appwrite didn’t help. Wondering if something is amiss at the MariaDB end?

TL;DR

User is experiencing an issue with a deleted attribute being "stuck" in a collection. They suspect it may not have been deleted successfully and suggest recreating the collection. They mention the importance of saving logs immediately when encountering weird events. Another user suggests checking the logs for any useful information, specifically mentioning a "Key column 'facility_id' doesn't exist in table" message. The user mentions not having logs from when the issue first occurred and tries deleting the attribute again, but no new logs are generated. They are asked to share the docker logs for the appwrite-worker-databases container and clarify if the logs provided are from after the

What's in the appwrite-worker-deletes docker logs?

Here you go

What's the attribute key?

facility_id

Are these logs from after the attribute became stuck only?

Can you also share the docker logs for the appwrite-worker-databases container?

I tried to delete it earlier today but that log is from after rebooting appwrite, so it’s possible it has no evidence of the defective delete. I just tried deleting again, but nothing seemed to be added to this log.

Ya...I would need the logs from when it happened to try to figure out the root cause

This last log seems to say something useful, “Key column 'facility_id' doesn't exist in table”

Now I know to save the logs immediately should something weird happens

Maybe the attribute didn't create successfully?

You could try to recreate the collection

Reply to this thread by joining our Discord

Reply on Discord