Your horizon-workers service shows a status of SUCCESS on our end, and its latest deployment is actively producing logs (running jobs as of a few minutes ago). Could you clarify what you mean by "stuck" and "showing old containers"? For example, are you seeing stale deployment entries in the Deployments tab, or is the service running outdated code despite a new deploy being triggered?

i'm been billed for a old service stuck running, please escalate to a human and track the start command: php artisan horizon

i can't see on dashboard and this is urgent

already deleted and created a new deployment but the stuck container still running, i don't know what to do, railway agent cant help

i completely recreated my infrastructure and the deleted services still growing, something is tuck and i'm paying for this!!!!!!!!!

still growing

still growing

i deleted the redis and recreated a new one, the old container stuck can't connect to redis,

please resolve that shit, this is unnaceptable

Hey, sorry about this — we can see orphaned containers from your old services that aren't terminating properly. We're looking into this directly to kill the stuck containers and make sure you're not billed for them. Can you share the project URL so we can identify all the orphaned instances?

https://railway.com/project/94cea665-13b5-46ae-993c-5665e3b32a50?

Hi there, apologies for the delay here. I've escalated this issue to our platform team to investigate.

still being charged for a stuck service

Why do you say it's stuck? You would still be on the hook to pay for the usage before it was deleted.