I make an update request to a collection. It returns a 500 status code even though the data looks updated in Appwrite Cloud dashboard. My request is pretty straightforward and is fired off via the web client in React:
return db.updateDocument(config.databaseId, config.mediaCollectionId, mediaId, serializedFields);
I'm writing stringified JSON into a string field that is within range of my character limit.
The error message is cryptic and I don't know how to move forward to resolving it. This is a problem for me because I have an onSuccess block that manages some internal caching in my application. It's not firing because of the error even though the data looks good.
Request:
Request URL:
https://cloud.appwrite.io/v1/databases/63a9465bf069da4ee9ef/collections/64ef71bcbf5f618e9511/documents/64f2ec0d1dd6d46ec25b
Request Method:
PATCH
Status Code:
500
Remote Address:
157.230.79.70:443
Referrer Policy:
strict-origin-when-cross-origin
Response:
{
"message": "Server Error",
"code": 500,
"type": "general_unknown",
"version": "0.10.56"
}
i get error 500 for update requests just now.. using the appwrite sdk.. it was fine before.....But the query operations seems fine though.... here's my log: Reloaded 9 of 2390 libraries in 230ms (compile: 52 ms, reload: 71 ms, reassemble: 85 ms). [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: AppwriteException: general_unknown, Server Error (500) #0 ClientMixin.prepareResponse (package:appwrite/src/client_mixin.dart:73:9) #1 ClientIO.call (package:appwrite/src/client_io.dart:373:14) <asynchronous suspension> #2 Databases.updateDocument (package:appwrite/services/databases.dart:123:17) <asynchronous suspension> #3 updateSite (package:registry_flutter_app/database.dart:151:10) <asynchronous suspension> #4 _UpdateSiteWorkTypeFormState.build.<anonymous closure> (package:registry_flutter_app/forms/update_site_worktype_form.dart:118:25) <asynchronous suspension> .. and it also happens in my webapp too..
Yeah, I just realized it's occurring for other queries as well that are using DB. It's not limited to the one I detailed above. These queries were working fine yesterday. π€
Wonder if it's related to the Cloud upgrade.
ya....i think this might be due to our maintenance. someone is looking into it.
i also got multiple 500 error: HTTPError: 500 Server Error: Internal Server Error for url: https://appwrite.rsstranslator.com/v1/databases/db_main/collections/t_rss/documents/64e969064178b9d1b4d1 And some function executions still in Processing
can you try again?
@telemetry and @versun would you also please try again?
@Steven itβs working now thank you
Yeah! It's working now. Thanks a lot
I'm still receiving the same error
I only see it in one area though. Earlier it was erroring out in all parts of the application.
What area? and will you be able to share the projectId that's having the issue
sorry I'm trying to play around with my app to figure out what parts. The area that's having a problem is the one I initially messaged about.
{
"message": "Server Error",
"code": 500,
"type": "general_unknown",
"version": "0.10.56"
}
``` Getting this right now. Same situation: updating a document with some fields and it's being saved properly but I'm getting a 500 in response.
For this collection.
https://cloud.appwrite.io/console/project-63a941b33d5b09aa6211/databases/database-63a9465bf069da4ee9ef/collection-64ef71bcbf5f618e9511
The data is saved, but you are getting 500?
Yup that's right. I just checked again. The operation returns a 204 for OPTIONS and then it returns a 500 for PATCH.
The data is updated in my collection.
@Steven now console seems to have some problems.. i deleted timestamp attribute but it's still there... and added new attributes and they have "processing"
I just checked 3 hours later and it seems to be fixed now. I'm not getting that error anymore.
the console seems to be working now after i got back..
Thanks!
Recommended threads
- [FEAT REQ] Bun runtime support
Instead of just Nodejs, it would be helpful to also add support for the Bun runtime which can speed up deployments by a ton.
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...
- NextJS builds sudden runtime_timeout
My builds suddenly stopped working. Activating old prebuilt snapshots work, but redeploying that same code produces builds that throw runtime_timeout FRA region