11401282-8a27-4c3a-b526-94dd63d86e9c

when clicking on the Runnning bit it says this

so it shouldnt say running, want to ensure I a not charged for it

We just didn't capture the container exit event, if you see that log, it is indeed stopped

Okay good good thx

is there any way to remove them? so they dont show? imo its a fe bug if the deployment was removed or finished it shuldnt say running anymore

unfortunately we don't yet have a way to force stop a job (even if it isn't technically running to begin with)

you could right click on the service to duplicate it and then delete the old service.

and question, would you happen to have app sleeping enabled on that service?

what do you mean app sleeping?

the app used to be running on a vps, its a simple bday reminder job for myself, at 9am check cal text me reminders sleep 24hrs, but I removed that part moved it to RW and use cron job to run it at 9am and its working now, but those two jobs still say running (the sleep part in code was removed before I added it to railway)

please check the service settings for the app sleeping option, is it enabled?

no should I?

i guess it wouldnt hurt as it knows via the cron job when to turn back on, so would save resources and money

please do not, it would not help and would make things worse, hence why i asked

cron jobs are already not runnig unless they are running

oh really

well no it isnt enabled all good

out of curiosity why would it hurt? because of the cold boot rebuilding the image each time?

the two settings are just not compatible

either way, we do not rebuild the image on cold boot, we simply run the already built image

ah fairs interesting to know

either way, I am happy to know that these are not actually running and eating my resources but would be good if it could be fixed in UI or otherwise that it no longer says Running and shows the loading and counts up in mins the time

we are actively working on improving the cron experience <:salute:1137099685417451530>

<:thanks:983662322771955712>