Function executions not getting logged but still executing successfully

Hello,

I have just upgraded on a self-hosted 1.8.1 to 1.9.0 and I have a strange bug where my functions are no longer showing executions in the console, however they are still running as I get proper responses when triggering them from a client but not from the console.

After running the upgrade command I tried the following steps to fix this:

1. I ran docker compose up -d --force-recreate to make sure my containers are new.
2. Updated the appwrite npm package and the cli and the appwrite-node for my functions
3. I deleted my function and created a new deployment with a new url for a simple function that logs the ip of whoever connects to it.
4. Tested it and got a proper response
5. Checked the executions and found no logs.
6. Modified the deployment text to verify that I am connected to the right function.

Something else I noticed is when I manually create an execution the log shows up but never resolves. With no errors.

Any idea on what else I could try?

Have you found a solution yet? I did notice the same problem after upgrading from 1.8.1 to 1.9.0 on my staging instance.

it's possible that your missing the new worker-executions container, iirc some others people had issue when running functions from the console without this container.

Could you also check the logs of every function related worker / task and the executor so we can maybe see a specific error

I just reverted to a backup I had of 1.8.1 for now. In the future I will probably start over with a fresh install of 1.9.0 and copy over the code in each of my functions.

I’m getting the same behavior, when I run a function using the domain url I don’t get execution logs, but when I run the function by SDK I do have it.

My event driven executions are not being logged although they are running.

Confirmed fix — @Ibaraki Douji was right, the missing appwrite-worker-executions container is the root cause.

When upgrading 1.8.1 → 1.9.0, Appwrite introduced a new worker service (worker-executions) that is responsible for persisting Execution docs for async triggers (events + schedule). HTTP-triggered executions keep working because they write synchronously through the main API container. Event and schedule triggers rely on this new worker — if it's missing from your compose file, the fn still runs (container spins up, handler executes, usage counter increments) but no Execution row is ever inserted. That's why the logs never appeared in the console.

Fix
Add this service to your docker-compose.yml (drop it between appwrite-worker-functions and appwrite-worker-mails):

appwrite-worker-executions:
image: appwrite/appwrite:1.9.0
entrypoint: worker-executions
<<: *x-logging
container_name: appwrite-worker-executions
restart: unless-stopped
networks:
- appwrite
depends_on:
redis:
condition: service_healthy
mariadb:
condition: service_healthy
openruntimes-executor:
condition: service_started
environment:
- _APP_ENV
- _APP_WORKER_PER_CORE
- _APP_OPENSSL_KEY_V1
- _APP_DOMAIN
- _APP_OPTIONS_FORCE_HTTPS
- _APP_REDIS_HOST
- _APP_REDIS_PORT
- _APP_REDIS_USER
- _APP_REDIS_PASS
- _APP_DB_ADAPTER
- _APP_DB_HOST
- _APP_DB_PORT
- _APP_DB_SCHEMA
- _APP_DB_USER
- _APP_DB_PASS
- _APP_FUNCTIONS_TIMEOUT
- _APP_SITES_TIMEOUT
- _APP_COMPUTE_BUILD_TIMEOUT
- _APP_COMPUTE_CPUS
- _APP_COMPUTE_MEMORY
- _APP_EXECUTOR_SECRET
- _APP_EXECUTOR_HOST
- _APP_USAGE_STATS
- _APP_DOCKER_HUB_USERNAME
- _APP_DOCKER_HUB_PASSWORD
- _APP_LOGGING_CONFIG

Then:

docker compose up -d
docker ps | grep worker-executions
docker logs appwrite-worker-executions --tail 30
Verify
Trigger an event-driven or scheduled function, then check MariaDB directly:

docker exec appwrite-mariadb mysql -u root -p"$ROOT_PASS" appwrite
-e "SELECT COUNT(*), `trigger` FROM __executions GROUP BY `trigger`;"
You should see trigger=event and/or trigger=schedule rows now.

Why the upstream installer missed it
I upgraded my compose manually from a pre-1.9 baseline, and the new worker-executions service wasn't documented in the upgrade notes. Anyone who did a docker compose up -d without pulling the fresh compose reference from the 1.9.0 release ends up missing this worker. Fresh appwrite/installer installs should include it by default.

Hope this unblocks everyone — took a while to trace because:

worker-functions logs Triggered function normally
runtime container (exc1-*) starts fine
usage stats increment
only the Execution row fails to persist silently

Hello. I've had similar issues and followed the steps outlined above. Existing functions I had are now able to run from the function page in the UI but running docker logs appwrite-worker-functions --tail 50 still returns Fetched 0 functions...

I've also created a new function just to test if the missing service worked but still having the same issue, at least it doesn't hang now and promptly returns a 500 error code. Running it via the SDK however works just fine.

Logs for the worker-executions are empty. I'm using mongodb instead of mariadb

Actually no, the SDK is now failing

This was the error for me as well. Seems to be somewhat reproducable when upgrading from 1.8.1 -> 1.9.0

in 1.9.0, the installer is missing the container, it's fixed for future releases, but will still remain with official way to install 1.9.0

what if you paste a fresh yml file?

Actually it looks like logs will be removed on self-hosted version 😕

https://github.com/appwrite/console/pull/3071

Hello @user I confirm that it works, thank yo som much ! is't verry helpful