When I use the web browser to view the collections in my database, the documents they contain are normally displayed within a few seconds. For a few days now, however, there has been one particular collection that takes several minutes to display; it only contains 12 very small documents. It is noticeable that 3 of them are invalid in the sense that the displayed ID does not exist. If I mouse-over them in the Browser, the DevTools start to display "404 (Not Found)"; see Screenshot with the big yellow 2. I cannot delete the documents via the WebBrowser. If I try to delete the document programatically using an API-Key, I get a 404 in response. If I retrieve all documents of the collections with the same API-Key via list(), the call is terminated at some point without result with an “ERR_EMPTY-RESPONSE” error; see Screenshot.
- what happened and how can I prevent this in the future?
- how can I clean the database of the invalid entries?
- what is the call to /backups/policies seen in screenshot 1?
Further information:
- Self-Hosted
- Appwrite 1.6.1
Recommended threads
- Local appwrite run functions --user-id n...
Hi, I'm running into an issue when testing Appwrite functions locally with user impersonation. I'm using a self-hosted Appwrite instance and running functions ...
- Selfhosted Github App installation
I've followed this guide: https://appwrite.io/docs/advanced/self-hosting/configuration/version-control to connect GitHub to my self-hosted Appwrite instance (1....
- User ID case sensitivity
I see that through REST (and SDK as well), getting a user is not case sensitive. And even though documentation does not clearly state that it is, the wording "V...