Invalid document structure: Unknown attribute (when attribute actually exists)
- 0
- Self Hosted
- Databases

I have had this issue where update document would throw me an unknown attribute exception. This happened after adding a new optional attribute. This new attribute did show up in the Appwrite console and was not in processing. I've tried to delete the attribute but it would then become stuck.
I've solved the issue by deleting the whole collection and recreating it. Deleting the whole collection is a scary process and is not something I can do on production. I'm now scared to add any new attribute to existing collections as it could randomly get me in this unknown attribute state.
It would be very helpful if someone could explain what cause the issue, if it's fixed in 1.5 and what I could do if it happens again.
I'm using Appwrite self hosted on version 1.4.13.
Recommended threads
- CSV Import not working
I am running 1.7.4, trying the sample book csv import. I get a pop up saying import started and then a quick follow up saying completed. Nothing ever appears ...
- ❗[Help] Function stuck in "waiting" stat...
Hi Appwrite team 👋 I'm trying to contribute to Appwrite and followed the official setup instructions from the CONTRIBUTING.md guide to run the platform locall...
- Help with 409 Error on Relationship Setu...
I ran into a 409 document_already_exists issue. with AppWrite so I tried to debug. Here's what I've set up: Collection A has 3 attributes and a two-way 1-to-m...
