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
- Sudden CORS Errors - Domain hasn't Chang...
I have an Appwrite project with two web apps configured, the first one has the hostname `*` and the second one I just added to test if it could fix the issue wi...
- Any way to temporarily bypass the email ...
Hey guys, any way to bypass the email verification to use the accounts again? i need to recover some projects that due to recent changes have been stopped, and ...
- Create a new paid tier
Current pricing seems reasonable enough about what is someone getting for 25$. But for some people most of these resouces are getting wasted. Like the bandwidt...