Upgraded to 1.4.13 and now none of my database writes trigger associated functions
True...
No, that's async
π
The hell ??? .. Let me check again.. I am completely lost at this point.. Let me delete all functions and redeploy them and test some more with crons and report back
Found something on redis logs. Not sure if its related
Yes, this could be related
Also Crons are getting executed though inconsistently.. This is a every minute cron
Any ideas on what I should do to address it ? Atleast try to resolve this migraine of an issue
Also I have a custom domain setup for my appwrite instance but functions domain is still localhost. Not sure if its relevant but trying to provide as much information as possible
[SOLVED] Upgraded to 1.4.13 and now none of my database writes trigger associated functions
Upgraded to 1.4.13 and now none of my database writes trigger associated functions
Is there a max number of functions that can run at the same time ? When I removed all function and added a subset it started working again and then as I deployed all it stopped ??
Verified, definitely the root cause. Brought the function count down to 5 and its up and running again. There seems to be a max functions limit after which functions become unreliable or are stopped from triggering. Will wait for your insights on the matter.
π§ shouldn't be no...
are they all listening on events?
added a subset
Why did you need to do this?
Nothing was working so I deleting all my functions and just deployed a couple that trigger on user registration and they started working as expected. Added a couple more, kept working, added all and things went back to broken. Now I deleted all functions and again added just 2 and they are working again.
Well in total there are 14 functions, 4 are cron and 5 listen to db events and 1 to user session. Remaining 4 don't listen to events but are triggered by other functions
maybe 1 of the functions is throwing an error and causing the rest to not execute
functions triggering off functions can be dangerous π
How so ? I did it for efficiency otherwise a single function runs quite long so I split it and now have it create an execution if needed
asynchronous execution?
Yup
that might not be as bad
Well now need to spend time figuring out what function is causing issues. Will do that tomorrow. BTW the test server is only 2 vcpus, can low core count and multiple functions running cause any issues ?
Also 1.4.5 never had this issue. The application would become quite slow and function executions piled up but triggers would never fail. That upgrade to 1.4.13 opened quite the can of worms for me
possibly if you're making a lot of network requests against Appwrite
