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
- AppwriteException: Invalid query: Query ...
```js console.log(typeof interaction.user.id) console.log(interaction.user.id) const user_check = await TablesDB.listRows({ databaseId: "db", ...
- Files access permissions
Am I right in understanding that file access permissions have been disabled (or broken again), and that shared access can now only be organized via tokens? Or i...
- functions custom domain issues in self h...
I’m running self-hosted Appwrite (Docker) behind Traefik with Cloudflare proxy (Full/Strict). Main domain works: https://app.printa4.in Function subdomains fa...