
you're getting this while executing an old function?

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

Well, old functions were removed completely and they were created again so I think its new functions now

I thought it was from users, relieved to know its from functions.

how are the functions being executed?

HTTP POST

Execution is going fine.

how exactly?

and can you confirm that that warning only shows up when you execute?

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

Flutter SDK

okd sdk, which is why the filter is running ππΌ

Yes OLD sdk it is, although is it troublesome?

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

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?

Ok

i created the issue: https://github.com/appwrite/appwrite/issues/6147

Solved: Appwrite container stops responding / gets stuck
Recommended threads
- Upgrading Appwrite 1.7.4 β 1.8.x: What H...
I'm currently running a self-hosted Appwrite v1.7.4 instance that still uses the old Collections/Documents database model. I noticed that starting from v1.8.x,...
- Appwrite's Docs MCP server DOWN?
Error code 502: bad gateway
- Domain not working
My domain [fork-fable.appwrite.network](https://fork-fable.appwrite.network/) returns a 500 even after deleting and redeploying. Other domains added in domains ...
