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
- In which format should i pass the date?
I have a column with the type `datetime`. So i want to know which format is suitable for passing the date
- Oauth issue
Hi, can anyone help me in the Oauth issue, Its working fine in dev but its showing Invalid redirect during production. I have check the redirect url and all. St...
- Google/Apple OAuth to show continue to "...
hi everyone, I am building a react-native app with expo and appwrite. I have setup an OAuth flow with Google and Apple following this doc (https://appwrite.io/b...