you're getting this while executing an old function?
Solved: Appwrite container stops responding / gets stuck
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 3: Container
I am not sure, its from appwrite container there is no logs from where its called
This call is only for when you're running functions
Rank 3: Container
Well, old functions were removed completely and they were created again so I think its new functions now
Rank 3: Container
I thought it was from users, relieved to know its from functions.
how are the functions being executed?
Rank 3: Container
HTTP POST
Rank 3: Container
Execution is going fine.
how exactly?
and can you confirm that that warning only shows up when you execute?
Rank 3: Container
How do I do that, there are like 100-200 executions per 2-3 minutes
Run
docker logs appwrite -f
Watch to see if they keep coming as your function being execute
Rank 3: Container
Flutter SDK
okd sdk, which is why the filter is running 👍🏼
Rank 3: Container
Yes OLD sdk it is, although is it troublesome?
Rank 3: Container
I would like you to point to the code from where its coming in appwrite, if you can that would be helpful
nah that's fine
doing this would be helpful. I'd really like to confirm that it's only the old create execution api call that's causing this
The error? here
Rank 3: Container
I dont think I can make sure that its coming from the function exeuction because that appwrite instance is in production.
What I can do is disable functions to see if its still coming, but that would make users angry.
ok then no worries
this warning isn't a big problem, but would you please create an issue so we can address it?
Rank 3: Container
Ok
i created the issue: https://github.com/appwrite/appwrite/issues/6147
Rank 3: Container
Solved: Appwrite container stops responding / gets stuck