
- I had a two way relation attribute.
- Deleted the two way relation attribute.
- Document Update fails as the relation key was still not deleted from one of the collection. Console doesn't show the deleted attribute but the underlying document still has reference to this attribute and fails with
Invalid document structure: Unknown attribute
- As the console doesn't show the attribute, I went ahead and created a new non relation attribute with the same key and it is now stuck in processing.
- Tried deleting the stuck attribute key using cli, although it says success the key is still not deleted.
I've ran out of options. How can we permanently delete a attribute so that document update succeeds without recreating the collection?
TL;DR
Developer had a two way relation attribute, then deleted it. Document update is failing because even though the console doesn't show the deleted attribute, the underlying document still references it. Trying to create a new non-relation attribute with the same key got stuck in processing. Deleting the stuck attribute key using CLI shows success but the key remains undeleted. How can the attribute be permanently deleted without recreating the collection to ensure document update success?
Solution: Instead of creating a new attribute with the same key, try updating the existing document to remove the stale attribute reference. If the CLI deletion is not working, reach out to the platform's support forRecommended threads
- Looking for Partner
I'm looking for partner for long-term collaborating. Of course, I'll pay for you. If you are interested, Please DM me.
- Issue - Migration From Cloud > Self Host...
Hi team, I’m trying to migrate a few of my Appwrite projects from the cloud to a self-hosted instance. These projects are currently in “archive mode” due to th...
- Why "You’ve reached the limit for your G...
Why did Appwrite send me this alert when the usage reached 10605%? Is it too late? Why not when reached 100% usage? And I can not pay for more usage described ...
