Hi! đđģ I'm using Appwrite Cloud and sometimes I randomly get a "fetch failed" error while executing a function:
at Client.call (/usr/local/server/src/function/node_modules/node-appwrite/lib/client.js:195:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Databases.listDocuments (/usr/local/server/src/function/node_modules/node-appwrite/lib/services/databases.js:1658:16)
at async Module.default (file:///usr/local/server/src/function/src/index.js:42:35)
at async execute (/usr/local/server/src/server.js:208:16)
at async action (/usr/local/server/src/server.js:225:7)
at async /usr/local/server/src/server.js:14:5```
Running the function again makes it time out:
```Synchronous function execution timed out. Use asynchronous execution instead, or ensure the execution duration doesn't exceed 30 seconds.
Error Code: 408```
The line that is referred to in the exception:
```database.listDocuments('5445545454454545', '3298329823923', [Query.equal('$id', user_id),]);```
This error rarely occurs. But when it does, it happens randomly and at random parts of the code. This potentially causes inconsistencies in my database. Because the function basically errors out in the middle of an operation and it's unpredictable when/where it happens.
Extra information: I don't use a custom domain or anything and I've never added/deleted/changed anything there. It's the default configuration.
Any idea what causes this problem?
is it still happening?
No, it seems to be working fine again now. It happened randomly before, but it happens rarely. That makes it difficult to find out what causes it I think. âšī¸ Either way, I'll report it here again if I ever notice that this error occurred again.
Still happening, but randomly. Added context here: <#1288301421447352330>
what runtime version?
I'm using "node-appwrite": "^12.0.1",.
Runtime version is node-18.0.
@memoonlite we added a patch to try and mitigate this issue, please let us know if you still see this,
That's great to hear! đđģđđģ
Sure. đđģđđģ I'm going to do a lot of development again today and I'll report it here if it happens again.
Seems fixed
Unfortunately not. âšī¸ It just happened a few seconds ago.
This error just occurred again:
at Client.call (/usr/local/server/src/function/node_modules/node-appwrite/lib/client.js:195:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Databases.listDocuments (/usr/local/server/src/function/node_modules/node-appwrite/lib/services/databases.js:1658:16)
at async Module.default (file:///usr/local/server/src/function/src/index.js:42:35)
at async execute (/usr/local/server/src/server.js:208:16)
at async action (/usr/local/server/src/server.js:225:7)
at async /usr/local/server/src/server.js:14:5```
It happens completely randomly.
I'll share with our team. Can you tell at which time didn't happen?
This is the execution log.
It's the first time that it happened today. It rarely occurs.
Recommended threads
- 403 The current user has been blocked.
Hello, I have a free plan; I've tried to access my project and I get the message "403 The current user has been blocked." I have database, sites, and auth in us...
- [Bug?] row_already_exists (409) after ma...
Hi, I'm experiencing a confusing issue with Appwrite Cloud Setup: A `tournaments` table with a composite UNIQUE index on (tournament_name, date). Steps to rep...
- Am getting "The current user has been bl...
Was working on my app FLUTTER WEB APP, and suddenly, I have been blocked.... What can I do ? When I try to sign in to the console, I get "The current user has ...