Updating a document is throwing a 409 conflict: "Document with the requested ID already exists."
- 0
- Self Hosted
- Databases
- Web
- REST API
Hello, I was trying to update a document with some data, but I keep getting this exception.
AppwriteException: Document with the requested ID already exists. Try again with a different ID or use ID.unique() to generate a unique ID.
Here is how the request looks like:
Request URL:
https://[url]/v1/databases/654203868c7fe15422da/collections/65c3c0105759db977ea3/documents/65c3c265cdef124f221a
Request Method:
PATCH
Status Code:
409 Conflict
Updating other documents is fine and has not caused me any issues. I must be doing something wrong, but I do not know what. I do not think the error message makes sense. Any help would be greatly appreciated.
could you show the implementation?
Sue, this is the document I was trying to update
{
"name": "Personal Information",
"employee_editable": true,
"enabled": true,
"for": "6542042f42dfcbf0f594",
"$id": "65c3c265cdef124f221a",
"$collectionId": "65c3c0105759db977ea3",
"$databaseId": "654203868c7fe15422da",
"$createdAt": "2024-02-07T17:48:21.843+00:00",
"$updatedAt": "2024-02-08T07:19:10.082+00:00",
"$permissions": [],
"form_fields": [{...}]
}
Note that form_fields is a relationship to another collection. I was trying to update the employee_editable field using
await databases.updateDocument(databaseID!, collectionID!, formDocumentID, {
employee_editable: formProperties.employeeEditable
});
which made a request I sent in the original message
Recommended threads
- preview domain 500 internal server error
Appwrite 1.8.1 The main domain is accessible, but the preview domain is inaccessible. Accessing the preview domain displays an Internal Server Error.
- [BUG] The cloud cannot be migrated to se...
The cloud cannot be migrated to self-hosting. The content of this post is exactly the same as [issue 11068](https://github.com/appwrite/appwrite/issues/11068) ...
- [Question] Is the development key applic...
I'd like to know if development keys are invalid in self-hosted environments? Is setting environment variables the only way to remove rate limits?