worker fails to launch since 2026.913.154316

(#836) Bug Needs triage self-hosting

Observed behaviour

Trying to start worker component starting from version 2026.913.183320 causes worker to error out with Error: Worker consumer workers_realtime was replaced during startup and exit, resulting in container going down. Downgrading to version 2026.912.205228 fixes this problem.

Reproduction steps

  1. Pull latest fluxer-worker image
  2. Try to run it

Build information

Not relevant

Platform

Self-hosting

Evidence

fluxer-worker[2344887]: {"level":"info","time":"2026-09-14T11:24:12.918Z","service":"fluxer-api","env":"production","msg":"Starting worker backend..."}
fluxer-worker[2344887]: {"level":"info","time":"2026-09-14T11:24:13.134Z","service":"fluxer-api","env":"production","msg":"Postgres KV client initialised for worker backend"}
fluxer-worker[2344887]: {"level":"info","time":"2026-09-14T11:24:13.135Z","service":"fluxer-api","env":"production","msg":"Worker lane configuration validated"}
fluxer-worker[2344887]: {"level":"info","time":"2026-09-14T11:24:13.135Z","service":"fluxer-api","env":"production","workerMode":"all_lanes","lanes":"realtime(10), unfurl(20), lifecycle(8), batch(12)","cronSchedulerEnabled":true,"msg":"Worker runtime configuration resolved"}
fluxer-worker[2344887]: {"level":"info","time":"2026-09-14T11:24:13.164Z","service":"fluxer-api","env":"production","msg":"Shared SnowflakeService initialised"}
fluxer-worker[2344887]: {"level":"info","time":"2026-09-14T11:24:13.167Z","service":"fluxer-api","env":"production","msg":"JetStream connection established"}
fluxer-worker[2344887]: {"type":"Error","message":"Worker consumer workers_realtime was replaced during startup","stack":"Error: Worker consumer workers_realtime was replaced during startup","stack":"Error: Worker consumer workers_realtime was replaced during startup\n    at JetStreamWorkerQueue.ensureConsumer (/usr/src/app/fluxer_api/src/api/worker/JetStreamWorkerQueue.ts:425:10)\n    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)\n    at async JetStreamWorkerQueue.ensureConsumers (/usr/src/app/fluxer_api/src/api/worker/JetStreamWorkerQueeue.ts:374:4)\n    at async JetStreamWorkerQueue.ensureInfrastructure (/usr/src/app/fluxer_api/src/api/worker/JetStreamWorkerQueue.ts:466:3)\n    at async startWorkerMain (/usr/src/app/fluxer_api/src/api/worker/WorkerMain.ts:236:3)"},"msg":"Failed to start worker backend"}
fluxer-worker[2344887]: {"level":"info","time":"2026-09-14T11:24:13.301Z","service":"fluxer-api","env":"production","msg":"Shutting down worker backend..."}
podman[2345020]: 2026-09-14 13:24:13.544954156 +0200 CEST m=+0.046745080 container died <container_id> (image=ghcr.io/fluxerapp/fluxer-api:2026.913.183320...)
podman[2345020]: 2026-09-14 13:24:16.643111543 +0200 CEST m=+3.144902458 container remove <container_id> (image=ghcr.io/fluxerapp/fluxer-api:2026.913.183320...)
systemd[722]: fluxer-worker.service: Main process exited, code=exited, status=1/FAILURE

1 comment

Sign in with Fluxer to comment and vote.
Comment by @MrRubberDucky
RexSystem 1 vote originally by @MrRubberDucky on GitHub OP
Just informing that it still does happen to me and I did not figure out a solution. NATS and everything starts up properly and I'm more or so forced to sit on this outdated version of worker as the latest one still fails to launch with the exact same error as above. Is there better way to debug this perhaps that I'm not aware of that could be useful in providing more information?