All five task-worker services in the "Alven AI Server" project show SUCCESS status for their latest deployments. Since you confirmed that deployments are being triggered for all five services but only task-worker reflects the updated code, this behavior is commonly caused by watch paths configured on the other services that don't match the changed files, resulting in new deployments that reuse the previous build. Please check each service's Settings tab to verify that task-worker-2 through task-worker-5 do not have watch paths set that would exclude your changed files, and also confirm they are all connected to the same GitHub repo and branch as task-worker.

Hello serezha13,

are watch paths set on any of them? if yes, make sure the patterns actually match the files you're changing, or just clear them if all services should deploy on every push ,, and are all 5 services pointing to the same branch?

also in the deployment history of services 2-5, do you see the deployments as "pending approval" or just not triggered at all?

Task-worker, task-worker-2, task-worker-4, and task-worker-5 have been removed, leaving only task-worker-3 running with 5 replicas. Despite this, logs from the removed services are still being received in Grafana via Locomotive. The workers were removed approximately 8 hours ago, but the logs are still coming through.