Hey there! We've found the following might help you get unblocked faster:

• 🧵 Hey my app keeps breaking and the workers returns ERRORS or rather stop

• 🧵 Application Crashes on Deployment - ModuleNotFoundError for MySQLdb

• 🧵 I'm having problems building because of next

If you find the answer from one of these, please let us know by solving the thread!

Hmmm,
Do you have anything in place which would OOM it if your resources went above a cap? I don't really see logs on our end for this.

I have logged memory usage at about the time it is killed and it is showing 11720 kib in use (11 megs). I have nothing programatic that would kill the process. here is the very end of the log:

2025-11-11T22:11:09.119850Z INFO worker_swaps: heartbeat: enqueued=0 flushed=0 flush_errs=0 redis_errs=0

Killed

worker exited with code 137

and the startup command:
sh -c '/usr/local/bin/laserstream-worker-swaps; code=$?; echo "worker exited with code $code" >&2; sleep 600'

Your worker process was terminated due to an out-of-memory (OOM) event. The reason you don't see this reflected in the memory usage graph is that our metrics polling interval is relatively long, so the process exceeded its memory allocation and was killed before the metrics system could capture and display the spike.