Does your code explicitly exit?

Oh - no that makes sense. Thank you. :)

No problem!

Hmm - I'm still seeing this despite explicitly existing.

I'm using process.exit() in a node app. I'm assuming that should work?

Exiting wouldn't have fixed the old running executions, since that was purely a display bug, though I have manually marked them as completed.

Additionally, your start command of cd apps/server && npm run convictionsCron is far from ideal for production environments.

Using cd is almost never the correct solution, and running your app via npm is not ideal either because npm does not propagate signals.

As far as I can tell your start command does stuff like prisma generate and injects env vars from dotenvx.

And for an optimised start command you can still do that, but in the end, node should be the single process that runs your javascript file.

That means transpiling with tsx during build and modifying your start command to run node directly, instead of through npm or dotenvx.

Ah ok thats really helpful info. thank you