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
- Type generation and Relationships in Typ...
Hello 👋, quick question about Type generation and Relationships in Typescript. There might be an "issue" using `createDocument` for relations, only the paramet...
- Unraid Deployment
Does anyone know how to point a production iOS app to an Appwrite Docker image I have on my Unraid server? I need a lot of storage, and having Appwrite on my Un...
- Can't create account in fresh self-hoste...
Clicking Sign Up shows this in the console: TypeError: undefined is not an object (evaluating 'W.validity')
