
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-many relationship with Collection B Collection B currently has no attributes
When I try to create a document, I get this: { "message": "Document with the requested ID already exists. Try again with a different ID or use ID.unique() to generate a unique ID.", "code": 409, "type": "document_already_exists", "version": "1.7.4" }
I have confirmed that I am not reusing IDs manually, so I suspect the issue is linked to how Appwrite handles relationship constraints under the hood. Has anyone run into something similar? Is there a specific way to structure the relationship doc creation to avoid this? All other help I found around 409 error has no clear note on how the issue was resolved and what directly caused it.
Any pointers would be appreciated. Thank you!
Recommended threads
- Is my approach for deleting registered u...
A few weeks ago, I was advised not to use the registered users' id in my web app. Instead, I store the publicly viewable information such as username and email ...
- ❗[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...
- Unable to create push providers - FCM or...
Currently unable to create a push provider for FCM or APNS.... https://github.com/appwrite/console/issues/2045 When uploading a file... FCM = Valid file retu...
