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
- Functions Problem
Whenever I run my AI Generate through Appwrite Functions, I am getting this Call Stack AIService.generateServer (src\services\ai\gemini.ts) next (<native>) ...
- Couldnt not do appwrite push tables
Not sure why i am not able to create my tables
- Frequent 500 Internal Server Errors - Pr...
PROJECT ID: 6951f2xxxxx1ee9e750a REGION: Singapore (sgp.cloud.appwrite.io) PLAN: Pro Our production application experiences **500 Internal Server Errors** mult...