I have a function that tries to add documents to a collection, first I wrote the function to check if the document exists by ID and if so, not add it. After the first run the async queue went sideways and all my other async function went on "waiting" for a few minutes, completely broke production. Then I did a "try catch" to write a document and if Doc ID exists it will catch but that also after first few runs sent rest of my async functions on "waiting". Just to be clear, working with Dart runtimes and the number of check can in the tens of thousands and fails can be as well but I would not expect the system to then take a 20 minute breather to recover.
Not sure why since none of the container logs point me to a direction as to why it happens but if you stress the function out with too much database checks and fails the whole thing goes on a waiting spree and everything async stops.
has anyone else faced this and has a work around ?
Async functions work via a queue. Is your first execution still executing?
Recommended threads
- router_deployment_not_found
I updated my function a few times and now i am getting the error: router_deployment_not_found I even reverted back to my original code but i am still getting th...
- Usage of the new Client() and dealing wi...
Hey guys, just a quick one - we had some web traffic the other day and it ended up bombing out - To put in perspective of how the app works, we have a Nuxt Ap...
- [Beginner] CLI --queries Syntax Error & ...
Hi everyone! I am a beginner with Appwrite and trying to use the CLI, but I'm stuck with a syntax error. Any guidance would be greatly appreciated! 🙏 **Enviro...